Search Announcements

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. Description adds search scope and filtering context but no extra behavioral details (e.g., pagination, rate limits). Acceptable given annotation coverage.

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?

Two concise sentences: first states purpose and filters, second provides concrete use cases. Front-loaded, no redundant content.

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?

Covers search purpose and filtering adequately for a search tool. Missing explanation of pagination or output format, but schema documents cursor and limit. No output schema, so some gap remains—acceptable but not perfect.

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 has 78% description coverage, adding detailed parameter explanations (e.g., NACE prefix logic, zero-padded kommune/fylke). Description only generically mentions filter types, adding no value beyond schema.

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 explicitly states the tool searches 'BRREG kunngjøringer across all Norwegian companies' (specific verb+resource+scope), lists filter types, and distinguishes from sibling 'firmaradar_get_company_announcements' which targets single companies.

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?

Description provides clear use cases ('trend analysis', 'radar-style monitoring') and implies broad vs per-company search via scope. Missing explicit 'when not to use' or alternative naming, but sufficient for context.

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