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

Annotations already mark the tool as read-only, so the description does not need to repeat that. It adds useful behavioral context beyond the schema by indicating that the tool returns publisher information ('who publishes what') and supports word-based search. No contradictions with annotations.

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 short and front-loaded with the key action, resource, and usage guidance. The trailing 'hint.' adds minimal noise but does not significantly harm clarity.

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 a fully described schema, a read-only annotation, and no output schema, the description provides enough purpose and usage context to call the tool correctly. It conveys the tool's role in finding publishers, which is the key contextual missing piece.

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 100%, so the schema fully documents all seven parameters. The description does not add parameter-level details, but it reinforces the core 'by words' search behavior. This meets the baseline expectation of 3.

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 a specific verb ('Search'), a concrete resource ('the national data catalogue I14Y'), and the intent ('to find who publishes what'). It also distinguishes itself from sibling listing tools by emphasizing free-text search by words.

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 explicitly says to 'use first' for finding who publishes what, giving clear contextual guidance. It does not explicitly name alternatives or exclusion conditions, but the intended usage is unambiguous enough for an agent to select it appropriately.

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