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

Annotations declare a non-idempotent, destructive mutation, and the description adds real context beyond that: the tender moves to Bidding, a six-step sprint is planned back from the deadline, an off-pipeline tender is added first, and the caller needs a Winquill account with a role that permits bid calls. These are exactly the side effects and auth prerequisites an agent must know before invoking.

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?

Front-loaded with the trigger condition, then side effects, then the exclusion, then the example — a sensible order with no filler sentences. It runs slightly long, since the six-step sprint detail and the example could be trimmed, but each sentence carries actionable information.

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 non-idempotent mutation with a nested answers object, the description covers trigger, exclusions, prerequisites, side effects and an example, while annotations carry the safety profile and an output schema handles return values. Nothing an agent needs in order to call this correctly is missing.

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 the baseline is 3; the description adds value by including a concrete example payload showing how tender_reference, decision and the nested answers object fit together. It does not, however, add anything beyond the schema for the optional reason or workspace fields.

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 — records the bid or no-bid call plus the team's answers and reason — and names the sibling it is not (assess_tender_fit). An agent can distinguish it from adjacent pipeline tools like add_to_pipeline or check_bid_readiness 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?

Explicit trigger conditions ('when the user's team has decided whether to bid'), an explicit exclusion ('Not for judging fit before the call, use assess_tender_fit'), and a procedural precondition ('Confirm the decision with the user before calling'). Nothing is left to inference.

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