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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false. The description adds critical behavioral context beyond those: the per-send human approval rail, no standing grant, exactly-once send, the card being the yes, and the fact that by_date is measured from approval not ask. It also explains the daily sweep and how the claim is rendered across surfaces. This is substantial added transparency. Minor deduction: it doesn't explicitly state what happens to the pin on release beyond 'deletes the pin', but that is covered.

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 dense but well-structured: a first sentence stating the core action, a second sentence on operator-only usage, then a compact explanation of the claim components, and a routing line plus a sensitive-tier block. It front-loads the most important information. It is longer than ideal, but every sentence carries meaningful content; the sensitive-tier block is essential for safe invocation. Slight deduction for density and the somewhat sprawling middle sentence.

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 destructive, operator-only tool with 9 parameters and no output schema, the description covers the essential context: when to call, what the approval flow is, what each claim component means, how disconfirmation works, and how the pin is read elsewhere. The absence of an output schema is compensated by the description's explanation of the derived read and the daily sweep. An agent has enough to decide whether and how to invoke this tool correctly.

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 baseline is 3. The description adds meaningful semantics beyond the schema: it explains the 8–280 char claim, the 7–180 day window rationale, the disconfirmation mechanism, and the release:true interaction. It also clarifies that note is not rendered in prompts and is neutralised on the derived read. This goes beyond the schema's field descriptions, so a 4 is warranted.

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 opens with a specific verb phrase — 'Pin, re-pin, or release this company's binding revenue constraint as a DATED, FALSIFIABLE claim' — and clearly distinguishes the three operations. It names the resource (binding revenue constraint) and the key attributes (dated, falsifiable), which separates it from generic constraint or commitment tools in the sibling list.

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 description gives explicit routing: 'Use when the operator says which constraint binds and until when' and 'Routing: Operator pins / re-pins / releases the binding constraint claim → use this'. It also states when not to use it implicitly by requiring operator input and a human-approved card, and it explains the re-pin semantics ('confirm-still-binds is a re-pin'). This is strong usage guidance.

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