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

No annotations are provided, so the description carries the full burden. It discloses caching (1h) and pricing ($0.01 per call), which are useful behavioral traits. It implies read-only behavior, but no explicit contradiction.

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?

The description is a single paragraph that efficiently conveys purpose, usage, output format, and behavioral traits. Every sentence adds value, and the query example front-loads essential context.

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?

Given no output schema, the description lists the fields in each notice (publication_number, title, etc.). It covers parameters, behavior, and pricing. For a tool with 4 optional params, it is fairly 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?

With 0% schema description coverage, the description adds meaning: 'cpv = 8-digit CPV code', 'country = 3-letter buyer country', and notes all parameters are optional. It also shows a usage example.

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 clearly states the tool finds 'Fresh EU public procurement notices from TED' and provides a query example. It distinguishes from sibling tools (e.g., French or UK company lookups) by specifying EU-wide 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 description explains the data source (TED, daily new notices), cache duration (1 hour), and pricing. It does not explicitly state when not to use, but the context and sibling names make it clear.

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