Hotjar

Typed function declaration. The platform reads ``chain_callable`` from the manifest to pick typed dispatch (direct ``app/func(args)`` call) vs. legacy ChatExtension LLM-router delegation. Defaults to ``True`` for ALL ``action_type`` values since v4.2.10, so the platform can deterministically execute the typed tool without giving the LLM a chance to summarise instead. ``effects`` declares the *intended* side-effect surface (``["create:note"]``, ``["delete:folder"]``, …). **Reserved / advisory:** the kernel does not currently consume it (no narrator / audit-ledger read today); it is retained as declared-intent metadata emitted into the manifest. ``id_projection`` declares the Pydantic params field that carries the resolved target id when this tool runs as a downstream chain step. Default empty — the platform falls back to a verb-prefix heuristic (``delete_note`` -> ``note_id``). Required for compound names where the heuristic produces a wrong field (``delete_notes_from_folder`` would naively yield ``notes_from_folder_id`` instead of ``folder_id``).

Typed function declaration. The platform reads ``chain_callable`` from the manifest to pick typed dispatch (direct ``app/func(args)`` call) vs. legacy ChatExtension LLM-router delegation. Defaults to ``True`` for ALL ``action_type`` values since v4.2.10, so the platform can deterministically execute the typed tool without giving the LLM a chance to summarise instead. ``effects`` declares the *intended* side-effect surface (``["create:note"]``, ``["delete:folder"]``, …). **Reserved / advisory:** the kernel does not currently consume it (no narrator / audit-ledger read today); it is retained as declared-intent metadata emitted into the manifest. ``id_projection`` declares the Pydantic params field that carries the resolved target id when this tool runs as a downstream chain step. Default empty — the platform falls back to a verb-prefix heuristic (``delete_note`` -> ``note_id``). Required for compound names where the heuristic produces a wrong field (``delete_notes_from_folder`` would naively yield ``notes_from_folder_id`` instead of ``folder_id``).

Typed function declaration. The platform reads ``chain_callable`` from the manifest to pick typed dispatch (direct ``app/func(args)`` call) vs. legacy ChatExtension LLM-router delegation. Defaults to ``True`` for ALL ``action_type`` values since v4.2.10, so the platform can deterministically execute the typed tool without giving the LLM a chance to summarise instead. ``effects`` declares the *intended* side-effect surface (``["create:note"]``, ``["delete:folder"]``, …). **Reserved / advisory:** the kernel does not currently consume it (no narrator / audit-ledger read today); it is retained as declared-intent metadata emitted into the manifest. ``id_projection`` declares the Pydantic params field that carries the resolved target id when this tool runs as a downstream chain step. Default empty — the platform falls back to a verb-prefix heuristic (``delete_note`` -> ``note_id``). Required for compound names where the heuristic produces a wrong field (``delete_notes_from_folder`` would naively yield ``notes_from_folder_id`` instead of ``folder_id``).

Typed function declaration. The platform reads ``chain_callable`` from the manifest to pick typed dispatch (direct ``app/func(args)`` call) vs. legacy ChatExtension LLM-router delegation. Defaults to ``True`` for ALL ``action_type`` values since v4.2.10, so the platform can deterministically execute the typed tool without giving the LLM a chance to summarise instead. ``effects`` declares the *intended* side-effect surface (``["create:note"]``, ``["delete:folder"]``, …). **Reserved / advisory:** the kernel does not currently consume it (no narrator / audit-ledger read today); it is retained as declared-intent metadata emitted into the manifest. ``id_projection`` declares the Pydantic params field that carries the resolved target id when this tool runs as a downstream chain step. Default empty — the platform falls back to a verb-prefix heuristic (``delete_note`` -> ``note_id``). Required for compound names where the heuristic produces a wrong field (``delete_notes_from_folder`` would naively yield ``notes_from_folder_id`` instead of ``folder_id``).

Typed function declaration. The platform reads ``chain_callable`` from the manifest to pick typed dispatch (direct ``app/func(args)`` call) vs. legacy ChatExtension LLM-router delegation. Defaults to ``True`` for ALL ``action_type`` values since v4.2.10, so the platform can deterministically execute the typed tool without giving the LLM a chance to summarise instead. ``effects`` declares the *intended* side-effect surface (``["create:note"]``, ``["delete:folder"]``, …). **Reserved / advisory:** the kernel does not currently consume it (no narrator / audit-ledger read today); it is retained as declared-intent metadata emitted into the manifest. ``id_projection`` declares the Pydantic params field that carries the resolved target id when this tool runs as a downstream chain step. Default empty — the platform falls back to a verb-prefix heuristic (``delete_note`` -> ``note_id``). Required for compound names where the heuristic produces a wrong field (``delete_notes_from_folder`` would naively yield ``notes_from_folder_id`` instead of ``folder_id``).

Typed function declaration. The platform reads ``chain_callable`` from the manifest to pick typed dispatch (direct ``app/func(args)`` call) vs. legacy ChatExtension LLM-router delegation. Defaults to ``True`` for ALL ``action_type`` values since v4.2.10, so the platform can deterministically execute the typed tool without giving the LLM a chance to summarise instead. ``effects`` declares the *intended* side-effect surface (``["create:note"]``, ``["delete:folder"]``, …). **Reserved / advisory:** the kernel does not currently consume it (no narrator / audit-ledger read today); it is retained as declared-intent metadata emitted into the manifest. ``id_projection`` declares the Pydantic params field that carries the resolved target id when this tool runs as a downstream chain step. Default empty — the platform falls back to a verb-prefix heuristic (``delete_note`` -> ``note_id``). Required for compound names where the heuristic produces a wrong field (``delete_notes_from_folder`` would naively yield ``notes_from_folder_id`` instead of ``folder_id``).