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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds one genuinely useful behavioral fact beyond them: the task is delivered into the call and must be accepted by that person, i.e. it is not executed synchronously. It does not address duplicate hand-offs, failure modes, or whether the recipient must currently be present.

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 short sentences, zero filler, with the core action front-loaded and the acceptance behavior immediately following. Nothing could be removed without losing information.

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 an open-world, non-idempotent write tool with no output schema, the definition covers intent and delivery model but omits what the caller gets back, what happens if the recipient declines or is absent, and whether repeat calls spawn duplicates. Adequate but with clear gaps for a cross-agent hand-off.

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%, and the description clarifies 'to' as a participant in the current call and 'task' as plain-words instructions, plus implicitly clarifies that 'meeting' refers to the current call. That is a marginal gain, but the undocumented 'meeting' parameter still lacks format/source guidance, so baseline 3 is appropriate.

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?

States a concrete verb+resource: hands a task to another participant's agent, scoped to the current call. An agent can distinguish it from generic messaging or task-update siblings like send_message or update_task without opening the schema, though it never names those alternatives explicitly.

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 context ('in the current call', 'another participant') but no when-to-use/when-not guidance and no pointer to alternatives such as update_task or send_message. The agent must infer the selection rule from context alone.

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