Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It discloses the write-tier approval flow, the optional side effect of closing/parking the source session, and that it composes other tools. It also adds the operational constraint 'Never invent paste rituals.' It does not detail kill_live_from semantics or what 'park' entails operationally.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences plus a bracketed approval note; the action and resource are front-loaded, the trigger phrases are concrete, and the composition/approval context earns its place. There is no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 10-parameter composite tool with no output schema, the description covers purpose, triggers, composition, constraints, and approval model well. Minor gaps: it does not state in prose that to_session_id and spawn_host are mutually exclusive (spawn vs. transfer), nor what the response contains, though the schema partially addresses the first point.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 10 parameters are documented structurally; the baseline is 3. The description adds high-level orchestration meaning (target existing session vs. spawn new one, optional close source) but no per-parameter detail beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The opening line 'Transfer work for THIS operator: push an instruction to a target coding session (or spawn one), optionally close/park the source' names a specific verb, resource, and scope. It also distinguishes itself from the sibling sub-tools by explicitly stating it composes create_attention_directive or request_attention_spawn + optional request_attention_close.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit trigger phrases ('move this to a fresh Grok', 'hand that off to Claude', 'continue on freedom-ai in a new tab'), providing clear when-to-use context. It names the composed sibling tools but does not state explicit when-not-to-use conditions (e.g., when to call request_attention_spawn directly instead of this composite).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.