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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations can't: that declining means Autopilot 'will not make it,' and that the reason field feeds the agency's learning loop. It leaves open whether a decline can be reversed or re-opened.

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?

Three short sentences, front-loaded with the action, then the trigger, then the parameter rationale. Nothing is padding; the parenthetical pointing to autopilot_status earns its place by resolving the only undocumented parameter.

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 three-parameter tool with no output schema and a destructive annotation, the description supplies the missing id source, the trigger condition, and the effect on Autopilot. What's absent—return confirmation and reversibility—is minor, though a one-clause note on whether the proposal can be re-proposed would close it fully.

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 coverage is 67% and the one undocumented parameter is the required proposal_id; the description closes that gap by telling the agent the ids come from autopilot_status. It also reframes note/reason as 'the person's own words' and 'why,' matching the schema's intent. It adds real value beyond the schema rather than repeating enum values.

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 ('Decline a change Autopilot proposed') and even points at where the proposal ids live (autopilot_status), which makes the workflow position clear. It does not explicitly contrast itself with close siblings such as autopilot_proposal_done or autopilot_dismiss_alert, so an agent still has to infer which terminal action applies.

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 a clear trigger condition: use it 'when the person says no.' That is a concrete usage context rather than an implied one. It stops short of naming the alternative actions (proposal_done, feedback, dismiss_alert) or stating when not to use it.

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