reject_proposal

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

With no annotations, the description carries real weight and does add value: it discloses that nothing is executed (a side-effect guarantee), and that a 401 on multi-user deployments is intentional rather than a bug, pointing at propose_action for the explanation. It stops short of stating whether a rejected proposal can be re-queued/re-approved or what state it ends in.

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?

Two short sentences with the destructive semantics front-loaded and the API route parenthetically appended; no filler. The '401 ... by design' clause is terse to the point of being slightly cryptic, but it is information-dense rather than wasteful.

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 single-parameter mutation tool with no annotations, the description covers the key risk (it does not execute) and the notable auth failure mode, and an output schema exists so return values need not be explained. Still missing are the post-rejection state of the proposal and how to obtain a valid proposal_id, which an agent needs before calling.

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%: proposal_id is a bare string with no format, example, or source. The description mentions proposals but never says where proposal_id comes from (presumably list_proposals or the propose_action response) or what form it takes, so it fails to 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 and resource ('Drop a queued proposal') plus the crucial qualifier 'without executing it', which separates it from approve_proposal and from propose_action. The endpoint path reinforces exactly what operation is performed, so an agent can distinguish it from siblings without opening a schema.

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?

Implicit usage is clear from 'queued proposal' + 'without executing it' — call this when you want to discard rather than run a pending proposal. The mention of 'see propose_action' gives a concrete cross-reference for the prerequisite/authorization context, though no explicit when-not-to-use statement or pointer to list_proposals for obtaining IDs is given.

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