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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false. The description adds useful behavior around retry identity ("Exact client_id and body identify retries") and validation scope ("retained source bytes and bindings, not reasoning or comprehension"), and it clarifies the lack of acceptance authority. However, it never explains what the destructive aspect actually means, such as whether an existing result can be overwritten, so the most important annotation remains underexplained.

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 short and front-loads the core action before adding validation and retry caveats. The sentences are dense but purposeful, with no obvious filler. The jargon ("retained source bytes and bindings") slightly reduces readability, but the structure is efficient.

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?

This is a complex destructive write with 11 parameters, nested objects, and no output schema. The description explains the general purpose and retry semantics, but it omits operational detail about validation failures, what is returned, and what happens to prior submissions. Given the schema's low description coverage and the destructive annotation, far more context is needed for an agent to call this safely.

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 only 27% across 11 parameters, so the description must carry more semantic weight. It mentions receipt, verdict, evidence references, recommendation_change, client_id retries, and assignment-linkage at a high level, but it does not explain status values, message_number, evidence_numbers, or the relationship between the required identifiers. Most parameters remain opaque even after reading 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?

The description uses a concrete verb ("Records") and names the resource: an assignment-linked saved answer plus receipt, verdict, evidence references, and an optional recommendation change. It also distinguishes the tool from acceptance workflows by stating "no acceptance authority is granted." It does not explicitly name sibling tools, but the purpose is still specific enough to separate it from read_relay, claim_relay, and confirm_acceptance.

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?

Usage is implied through "assignment-linked" and the retry note about exact client_id and body, but there is no explicit when-to-use or when-not-to-use guidance. The phrase "no acceptance authority is granted" hints that acceptance requires a different tool, probably confirm_acceptance, without naming it. This is enough to suggest context but not enough to route an agent confidently.

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