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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the 'FREE beta' status, which is a useful caveat about reliability/availability, and mentions the expert-query syntax, which hints at query complexity. However, it does not disclose behavior like result limits, error handling, or the fact that the query syntax may be complex for non-experts. With annotations covering the main behavioral traits, a 3 is appropriate.

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 sentence, front-loaded with the key action ('Search EU Tenders Electronic Daily notices') and the query syntax. The 'FREE beta' prefix is arguably unnecessary but short. It is concise and readable, though it could be slightly improved by removing the marketing-style prefix.

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?

For a simple two-parameter search tool with read-only annotations, the description is mostly adequate. However, it does not explain the 'basic' vs 'evidence' distinction that is evident from sibling tool names, nor does it describe the return format (no output schema exists). An agent would benefit from knowing that this is the lightweight/basic search and that 'eu_ted_search_evidence' exists for more detailed or evidence-oriented queries. The lack of output schema makes the missing return-format context more significant.

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 50%: the 'query' parameter has a description ('TED expert-search query syntax'), but 'limit' has no description. The tool description adds the context that the query syntax is 'expert-query syntax', which reinforces the schema's parameter description but does not explain the limit parameter's semantics or default behavior. With half the parameters undocumented in the schema and no additional detail in the description, the description only partially compensates.

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 verb ('Search') and resource ('EU Tenders Electronic Daily notices') and mentions the query syntax ('TED expert-query syntax'). It distinguishes the tool as a basic search variant, though it does not explicitly contrast with the sibling 'eu_ted_search_evidence' tool. The 'FREE beta' prefix is a minor distraction but does not obscure the core purpose.

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 implies usage for searching EU TED notices and notes the query syntax, but it does not explicitly state when to use this basic variant versus the 'eu_ted_search_evidence' sibling. There is no mention of exclusions, alternatives, or conditions that would guide an agent to choose this tool over others. The context signals and sibling list suggest a basic/evidence split, but the description itself does not articulate it.

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