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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds a genuinely beyond-annotation fact: all bids on the tender are declined as a side effect, and the 'open' qualifier implies an eligibility precondition. It stops short of saying whether the action is reversible or whether bidders are notified.

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 compact clause packs the actor, action, precondition, and side effect with zero filler, and the consequence is front-loaded alongside the verb.

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 one-parameter destructive mutation with full annotation coverage and no output schema, this covers the essentials: who may call it, what it acts on, and the collateral effect on bids. Only small gaps remain, such as irreversibility and bidder notification.

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?

One parameter at 100% schema coverage; the schema already tells the agent where a tender_id comes from (list_tenders or post_tender). The description adds nothing about the identifier format, so baseline 3 is correct.

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 (withdraw) and resource (an open tender), plus the audience constraint (Poster) and consequence (all bids are declined). This clearly distinguishes it from accept_bid, get_tender, and list_tenders.

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 word 'open' implies a precondition (the tender must still be open, not yet awarded), and 'Poster:' implies a role restriction. But no alternative is named and no explicit when-to-use/when-not guidance is given, so the agent must infer that this is not the path for awarding a tender.

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