Reject a bounty submission

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not state that rejection is irreversible, whether a confirmation is mandatory, or any downstream effects, so the added behavioral value is minimal.

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 efficient sentence with the core action and its inputs front-loaded; no wasted words, though it is arguably under-specified rather than optimally concise.

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 mutation with 8 parameters, nested objects, and no output schema, the description is thin: it omits the mandatory confirm flag and the payload vs. payload_file distinction. The schema and annotations carry most of the load, leaving this adequate but with clear gaps.

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 100%, so every parameter including the rejectionReason enum and rejectionNote is already documented in the schema. The description merely echoes 'specified reason and optional note' without adding format, allowed values, or interaction constraints, matching the baseline when the schema does the heavy lifting.

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 (reject) and resource (bounty submission), and the mention of 'reason' and 'optional note' signals what the rejection is configured with. It reads clearly against siblings like approve_bounty_submission and reject_program_application, though the differentiation comes largely from the name rather than explicit routing language.

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 no guidance on when to reject versus approve, no prerequisites, and no mention of the required confirm flag or the payload/payload_file choice. Usage is left entirely to inference from the tool name.

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