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

Annotations already declare readOnly=false, destructive=true, idempotent=true, so the safety profile is covered. The description's real contribution is countering the natural reading of 'countersignature' by clarifying that no signature is produced, which is genuinely useful. It still says nothing about what state is overwritten by this destructive write, required permissions, or offer-generation prerequisites.

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 no filler. The second sentence earns its place by preventing a specific misreading. It is efficient but under-specified rather than genuinely concise.

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 destructive, 8-parameter mutation with no output schema and 0% parameter documentation, the description is far too thin — an agent cannot know what values to supply for mode, generation, or user_id, nor what the call changes. Only the read/write scope is clarified.

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% across 8 parameters, so the description must carry the burden and it carries none. Nothing explains mode (none/pre_sign/post_candidate), user_id nullability, confirmed, refresh_recipient, or the role of idempotency_key and generation — the enum values are the only hint, and they come from the schema, not the description.

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?

The clause 'This does not sign the offer' acts as an implicit when-not hint — an agent knows not to reach for this expecting a signing action — but no positive trigger, prerequisite (e.g. offer state), or named alternative is given. Usage is implied rather than stated.

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