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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description earns credit by resolving that ambiguity: it explains that an interpretation is built and unread words are retained, but 'nothing is sent or ordered.' It also discloses the response behavior (each value records its source words, conflicts come back as a single question). It stops short of covering retry/idempotency behavior, which the schema handles.

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 core action and the structured-result behavior are front-loaded, and the two routing sentences at the end are the most decision-relevant. The opening sentence is long and stacks several colons/parentheticals, which costs some scannability, but no clause is filler.

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?

With four parameters, nested requirement credentials, no output schema, and a stateful continuation model, the description supplies the return semantics (structured fields with provenance, one clarifying question) that the absent output schema would otherwise need to carry. Retry semantics for turn_id remain solely in the schema, which is acceptable given full coverage.

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 the schema already documents utterance, turn_id, timezone, and the nested id/token. The description adds only the framing that the requirement object comes 'from the first answer' to continue a conversation, which is a small increment over 'The requirement to continue' in the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The description states a specific verb and resource: taking the buyer's requirement 'in their own words' and reading it into a structured requirement. It distinguishes itself from send_requirement (which sends) and submit_request (for already-structured fields), so an agent can pick it out of a large sibling set without opening any schema.

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?

It gives explicit routing rules: use this when you have free-text words, use submit_request when you already have structured fields, and use send_requirement when the buyer says to send. It also explains continuation via the requirement id/token from the first answer. This is the when/when-not/alternatives pattern done well.

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