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

With no annotations, the description carries the burden and does disclose key behavioral traits: the $0.09 cost via x402, live data, source (TED database), return fields, recent-first ordering, and total match count. It doesn't mention rate limits or error handling, but the core behavior is well covered.

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 two sentences, front-loaded with cost and purpose, and every sentence adds value. No redundancy or filler.

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?

Despite having no output schema, the description explains return values (title, country, publication date, notice link, match count) and ordering. It doesn't cover pagination or max result limits, but for a straightforward lookup tool with 3 parameters, it is largely 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 67% (q and months have descriptions). The description adds meaning by clarifying q as 'keyword/sector' and mentions lookback months implicitly through 'recent-first', but doesn't add detail beyond the schema's existing parameter descriptions. This is adequate but not exceptional.

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 states a specific action ('live public procurement tenders') with a clear resource ('official EU TED database') and scope ('all 27 EU member states'). It distinguishes itself from sibling tools by emphasizing EU-specific public-sector tenders and European opportunity targeting.

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?

It provides clear context: 'The overseas opportunity layer for sales, BD & research agents targeting European public-sector spend.' This tells when to use it, though it doesn't explicitly name alternative tools or state when not to use it.

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