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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false). The description adds one genuinely useful behavioral fact, the required 'tasks:write' scope, which annotations do not convey. It says nothing about the fact that create is non-idempotent and that idempotency_key is the escape hatch, which is behaviorally significant for a create operation.

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, front-loaded with the action and followed by the auth requirement. Nothing is wasted, but the brevity verges on under-specification rather than crispness.

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 6-parameter creation tool with no output schema, the description is thin: it doesn't say what is returned (a task id? a task object?), how idempotency_key interacts with the non-idempotent annotation, or what assign_to_agent_id and client_encrypted do in practice. An agent would need to open the schema and guess.

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 only 50%: title, workspace_id, and assign_to_agent_id carry no descriptions. The description does not compensate at all, adding no meaning for any of the 6 parameters, including the important assign_to_agent_id routing and client_encrypted envelope flags.

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 specific verb+resource ("Create a task") plus a qualifier ("for handoff") that hints at intent. An agent can distinguish it from list_tasks/claim_task/complete_task by the verb alone, though the description never explicitly contrasts those siblings.

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?

"For handoff" implies a context of use, and "Requires scope 'tasks:write'" gives a hard prerequisite. However, there is no explicit when-to-use guidance, no mention of when not to use it (e.g. versus claim_task), and no reference to alternative tools.

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