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 adds only "Free" and the fact that notices are "current", with nothing on rate limits, auth, or result volume despite openWorldHint implying an external live source.

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 tight sentence front-loads the cost cue and the core action with no filler. It is efficient, though its brevity borders on under-specification for a three-parameter search tool.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. Still, with 33% parameter coverage and no routing guidance among many sibling tools, the definition is minimal rather than 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?

Schema coverage is only 33%: country is documented in the schema, while keyword and limit have no descriptions. The description restates that keyword and buyer country act as search filters but adds no format, matching behavior, or meaning for limit (capped at 10), so the low-coverage gap is not compensated.

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 (Search) and resource (current EU TED procurement notices) with the filtering dimensions (keyword, buyer country). It is clear on its own, but it never distinguishes itself from the closely related sibling shadowgraph_procurement_opportunity, so an agent must guess which procurement tool to pick.

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 "and/or" phrasing implies the two filters are optional and combinable, and "Free" hints at a cost boundary, but there is no explicit when-to-use, when-not-to-use, or named alternative against shadowgraph_procurement_opportunity. Usage 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.