chap.handoff.decline

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Decline a proposed handoff' and mentions the reason/suggestion fields, but does not disclose side effects, that the reason is recorded for the proposer, whether the action is reversible, or that already-finalized handoffs produce error -32051. This is a meaningful gap for a state-changing tool.

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 a single, concise sentence that front-loads the core action and covers the two key semantic points: a reason is expected and a suggestion is optional. There is no wasted wording or repetition of schema details.

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 handoff-decline mutation with no annotations and no output schema, the description is too sparse. It omits behavioral context, error states, and what happens after declining. An agent is left without enough information to predict side effects or handle edge cases like already-accepted handoffs.

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 parameters are already well documented. The description adds mild value by emphasizing that the reason is central and the suggested_target is optional, but it does not add meaning beyond what the schema already provides. 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?

The description states a specific verb ('Decline') and resource ('a proposed handoff'), with clear modifiers explaining that a reason is required and a suggestion is optional. This unambiguously differentiates it from sibling tools like chap.handoff.propose and chap.handoff.accept.

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?

The usage context is implied: use this when declining a proposed handoff. However, the description does not explicitly state when not to use it, nor does it mention alternatives such as chap.handoff.accept or chap.decide.reject. The guidance is adequate but not explicit.

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