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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the retry protocol detail and the payment/dispatch limitation, which is useful, but the idempotency guidance largely restates the idempotentHint annotation and no failure or delivery behavior is described.

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?

Three short sentences with the core action front-loaded, followed by the retry constraint and the exclusion. No filler; the only minor slack is that the retry sentence overlaps the schema's own idempotencyKey description.

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 four-parameter mutation tool with no output schema and 50% param coverage, the description covers purpose, retry semantics and an exclusion, and annotations carry the safety profile. It still leaves what taskId identifies and what happens on send failure unexplained, so it is adequate but 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 description coverage is 50%: idempotencyKey and requestToken are already documented in the schema, and the description's retry sentence echoes the schema's own idempotencyKey wording. The undocumented body and taskId parameters are not clarified, so the description adds little beyond what the schema supplies.

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 (send) and resource (a clarification on one task), and the scope constraint 'on one task' distinguishes it from broader sibling tools like submit_task or accept_quote. It stops short of explicitly naming which sibling to use instead, so it is clear but not sibling-differentiating at the top level.

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?

Provides an actionable retry rule (reuse the idempotency key with identical text) and an explicit exclusion ('cannot authorize payment or dispatch through text'), which is genuine when-not guidance. It does not say when to prefer this over sibling tools such as submit_task, but the exclusions are clear.

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