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

With no annotations, the description carries the behavioral burden and adds meaningful traits: the 1-credit cost, the Blind Mode ingestion limitation, and the AND-combination/full-text behavior. It does not state response structure or explicit read-only status, but nothing contradicts the query semantics and the main operational constraints are surfaced.

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?

Three compact sentences lead with the data source and scope, then add Blind Mode, filter semantics, and cost. Every sentence adds non-redundant information and there is no 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?

For a 16-param tool with no output schema and no annotations, the description gives a solid orientation but omits return shape, pagination behavior, supported value formats for non-date filters, and a clear explanation of how Blind Mode affects query fields. These gaps are material for correct invocation, so it is not fully 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?

Input schema description coverage is 0%, so the description must compensate; it does explain that q covers all text fields and that filters combine with AND, and it names the core filter categories. However, it leaves details like CPV code format, notice_type/procedure_type values, and pagination behavior undocumented in prose, relying on parameter names and schema types to carry the rest.

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?

Description clearly identifies TED/EU procurement notices as the resource and names meaningful data fields (buyer, country, CPV codes, values, deadlines), which distinguishes it from the UK-focused sibling query_uk_tenders. It lacks an explicit verb like 'search' or 'return' and uses the value-proposition phrase 'normalized for bid intelligence' instead of a direct operation statement.

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 gives operational semantics—filters combine with AND and q searches all text fields—and the EU scope implies the tool is for EU procurement rather than the UK tenders sibling. However, there is no explicit when-to-use/when-not-to-use guidance or named alternative, so the agent must infer regional routing from the title and sibling list.

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