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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations: it is a paid call ($0.02) and it enumerates the provenance and award fields, giving agents a clear picture of the returned data without an output schema.

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 front-loaded sentence packs endpoint, pricing, core function, and a detailed field list without redundant words. The HTTP verb and cost are placed at the very start for quick scanning.

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?

No output schema exists, but the description compensates by listing the major response groups (buyer, CPVs, deadline, value, awards/lots, winners, provenance source/TED URL). With parameters documented in the schema and safety covered by annotations, nothing essential is missing for an agent to invoke this tool correctly.

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 100%, so the schema fully documents id, client_key, and payment_token. The description only restates that the tool fetches 'by id' and does not deepen meaning beyond the schema, so the baseline of 3 is appropriate.

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 opens with the endpoint and 'Full tender detail by id', then enumerates the payload (buyer, CPVs, deadline, estimated value, awards/lots, provenance). This clearly names a specific verb/resource and distinguishes it from sibling list/search tools like search_tenders and get_company_awards.

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 phrase 'by id' makes the precondition explicit and implies this tool is for retrieving complete records once an identifier is known, rather than for discovery or search. It does not explicitly name alternatives or exclusion rules, so it lacks the full when-not-to guidance of a 5.

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