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

Annotations already declare idempotentHint=true and destructiveHint=false; the description reinforces idempotency with a precise rule ('Calling again with the same fix and description returns the existing record'), which is more specific than the flag alone. It doesn't cover auth requirements or rate limits, so it adds context without fully carrying the behavioral burden.

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 sentences, zero filler, with the core action and the idempotency behavior front-loaded. Every clause (source of IDs, downstream consumer, repeat-call behavior) carries distinct information.

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?

No output schema exists, yet the description still tells the agent what a repeat call returns, and it links the write to the verification tool that consumes it. For a 5-param, single-required-param write tool, nothing essential is missing.

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 all five parameters and the one-of relationship between gap_id and content_draft_id. The description restates that pairing and points at the originating tools but adds no format or constraint detail beyond the schema, matching the baseline 3.

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 resource ('Records that a fix shipped') and pins the identifying keys to their source tools ('gap_id from list_fix_opportunities or a published content_draft_id'). It also distinguishes itself by naming the downstream reader, get_fix_verification, so an agent can place it in the workflow without consulting siblings.

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 clear context for when to call it: after a fix ships, using IDs sourced from list_fix_opportunities or a content_draft_id, and explains the payoff is measurement via get_fix_verification. No explicit when-not-to-use or exclusion conditions are given, which keeps it short of a 5.

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