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

The annotations already specify readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful context that sending is out of scope and requires preview and confirmation, but it does not explain what happens to existing drafts or revisions, permissions needed, or other mutation side effects.

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?

The description is two short sentences with no filler, and the key constraint about sending is front-loaded. It is efficient, though the first sentence largely repeats the title.

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 non-read-only mutation tool with required parameters and no output schema, the description is too thin. It does not explain required inputs, what is returned, how existing drafts are affected, or what the replacement draft represents.

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 0%, so the description must compensate for three undocumented parameters: offer_id, request_id, and idempotency_key. It mentions none of them and gives no format, meaning, or constraint guidance.

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?

Tautological: description restates name/title.

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?

No guidance is given on when to use this tool versus alternatives such as yardstick_offers_update, yardstick_offers_cancel_revision, or yardstick_offers_create. The note that sending requires separate preview and confirmation is behavioral context, not a usage rule.

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