reject_payouts

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

With no annotations provided, the description must disclose behavioral traits. It indicates a PATCH mutation, but does not mention side effects, authorization requirements, reversibility, or any destructive behavior. The reference to approve_payouts is insufficient to fill this gap.

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 concise (one sentence), but it is too sparse to be considered well-structured. It front-loads the action, but lacks essential details that could be included without adding verbosity.

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?

Given the tool's complexity (8 parameters, low schema coverage, no output schema, no annotations), this description is severely incomplete. The agent cannot reliably invoke this tool based on the provided information alone.

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?

The description adds no meaning to the 8 parameters beyond what the input schema provides. Schema description coverage is only 38%, and the description does not compensate by explaining key parameters like dry_run, confirmed, or date filters.

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 clearly states the action 'Rejects payouts' and provides the HTTP endpoint, distinguishing itself from the sibling 'approve_payouts' by referencing its body rules. However, it lacks additional detail about what rejection entails.

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?

No guidance on when to use this tool versus alternatives like 'approve_payouts'. The description only mentions 'Same body rules as approve_payouts', which refers to parameter structure, not usage context.

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