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

Annotations already mark this as destructive, and the description reinforces that by saying the bid is 'Dropped' and 'cancelled'. It adds useful behavioral context: only unpaid bids can be cancelled, paid bids are decided by the board, and an Authorization Bearer JWT is required.

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?

Three short sentences with no filler. The core action is front-loaded, followed by an important constraint and the auth requirement. Every sentence earns its place.

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 simple one-parameter destructive tool, the description covers the target, the precondition, the boundary on paid bids, and auth. It does not describe the result or side effects beyond cancellation, but given the simplicity and the destructive annotation, this is nearly complete.

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 schema only provides 'id' as an integer with no description, and schema coverage is 0%. The description implies that 'id' refers to one of the caller's unpaid bids, which adds some meaning, but it does not explain how to obtain this id or what happens if it is invalid.

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 uses a specific verb ('Drops') and resource ('one of the caller's bids that is still awaiting funds'), making the operation unmistakable. It also distinguishes the unpaid-bid case from paid bids, which are handled by the board, helping differentiate this from related bid tools.

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?

It clearly states when to use the tool: for the caller's own bids that are still awaiting funds. It also gives an explicit exclusion: paid bids are not cancelled here. It does not name a specific alternative tool, but the when/when-not guidance is clear enough.

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