deny_payment

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

No annotations are provided, so the description carries the full burden. For a mutation tool it omits whether denial is reversible, whether funds are released or held, what authorization/ownership check is enforced, and what error occurs on a non-pending request.

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?

A single front-loaded sentence with no filler, and the actor and precondition come before the action. Its brevity is appropriate in form, though it leaves gaps elsewhere.

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?

A mutation tool with no annotations, no output schema, and undocumented parameters sits alongside approve_payment and revoke; the description should explain the resulting state and error conditions. It covers only the one-line action, leaving an agent unable to call it confidently in edge cases.

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 0% and the description says nothing about request_id — no format, source, or where to obtain it. The single parameter is only guessable from its name, so the description does not compensate for the coverage gap.

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 (denies) and resource (payment request), plus the actor (owner) and precondition (pending), which implicitly separates it from approve_payment. It stops short of naming the sibling alternative explicitly, so it is clear but not fully differentiated.

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 phrase 'pending payment request' and 'Owner' imply the state and role preconditions for use, and 'denies' contrasts with approve_payment. However, it never states when to deny vs. revoke or what happens if the request is not pending — the guidance is only implied.

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