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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description still adds real context beyond them: the exact payload fields returned and the authentication/quota note that it 'uses the free tier, or the caller's API key.' It does not say what happens when the notice ID does not exist.

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 sentence with the identity of the resource front-loaded and the returned fields compressed into one list. No filler, no restatement of the title.

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?

With one fully documented required parameter, no output schema, and annotations carrying the behavioral profile, the description is nearly sufficient; listing the return fields is valuable precisely because no output schema exists. Missing only error/not-found behavior, which is minor for a single-record lookup.

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% and the notice_id parameter already carries a format pattern and an example, so the description's phrase 'publication number' adds little beyond it. Baseline 3 applies since the schema does the work.

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: fetch one TED contract award notice by its publication number, and enumerates what the record contains (winners, buyer, value, CPV, dates, lots, link, proof). The singular 'one ... notice' implicitly contrasts with the plural sibling eu_contract_awards, but the alternative is never named, so an agent must infer the distinction.

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?

'By its publication number' implies the caller must already hold a TED notice ID, which points toward use after a search, but the description never says when to prefer this over eu_contract_awards or what to do if only a keyword is available. Usage is inferable rather than stated.

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