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

With no annotations, the description carries the full burden. It does disclose the downstream effect well — the recipient sees the task in the call and forwards it to their Claude with one press — which is real behavioral context. It says nothing about what happens if the name doesn't match a participant, whether the handoff is confirmable or reversible, or what the caller observes on success or failure.

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?

Two sentences with zero waste: the action and its effect are front-loaded, followed immediately by the one non-obvious naming constraint. A minor marketing tone ("with one press") but it conveys useful mechanics rather than filler.

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 three-required-parameter action with no annotations and no output schema, the description explains the mechanism and the naming requirement but omits failure behavior, what happens if no such participant exists, and what the caller gets back. Adequate to attempt a call, not complete.

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 coverage is 67%; `to` and `task` are documented in the schema, and the description largely repeats them. The undocumented `meeting` parameter is only obliquely covered by "from the call you are in," which hints it is the current call but does not confirm the identifier format. Net effect is roughly baseline.

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 description gives a specific verb and resource: it hands a task off to another participant's agent from within the current call. That is clearly distinct from speak, send_message, or send_notetaker, though the description never names a sibling to sharpen the contrast.

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?

"From the call you are in" implies the operating context (an active call with other participants) and "Name the person as they appear in the call" gives a usage constraint. However, there is no explicit guidance on when to use this instead of send_message or a task tool, and no stated preconditions or exclusions.

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