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

Adds real context beyond the annotations: the rewrite happens asynchronously in the background, the answer is re-marked, and the user is told when it's done. It also discloses the commercial model (first ten rewrites included, then draws on the workspace allowance) and the account requirement. It does not say whether the pre-rewrite answer is recoverable, which matters given destructiveHint=true.

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?

Front-loaded with the trigger condition and a concrete example, then the async behaviour, then cost and prerequisites, closing with the guard rail. Every sentence carries distinct information with no repetition of the schema.

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?

An output schema exists so return values need not be described, and the description still covers the async completion signal, the billing implication and the readiness precondition. For a five-parameter mutation tool this is as complete as an agent needs.

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 100%, so draft_id, question, workspace, instruction and tender_reference are all already documented, including the fallback behaviour when draft_id is omitted. The description's examples loosely illustrate what belongs in question and instruction but add no new semantics; 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 specific verb and a tightly scoped resource: rewrite one answer in a bid Winquill drafted. The quoted example utterances ("make Q3 shorter", "use the Glasgow contract as the example in 2.1") make it unmistakable versus siblings like draft_bid_response, continue_bid_draft and review_bid_draft.

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?

Gives concrete trigger utterances and an explicit exclusion ("Do not use before the draft is ready"), plus the prerequisite of a Winquill account. It stops short of naming the sibling to use instead when the draft isn't ready or when the user wants a full redraft rather than a single-answer rewrite.

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