Get Company Announcements

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds a critical behavioral detail: free-text fields are wrapped in <untrusted_content> tags to prevent prompt injection from BRREG-sourced text, which is valuable beyond 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?

Two sentences: first states purpose, second adds security context. Efficient, front-loaded, and no unnecessary text. Every sentence earns its place.

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 the simple input (single parameter with full schema coverage), no output schema, and ample annotations, the description adequately covers purpose, examples, and security behavior. No missing critical information for a list tool.

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 100%, with 'orgnr' described as '9-digit orgnr.' The description does not add further meaning or formatting details beyond the schema, so baseline score of 3 is appropriate.

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 uses specific verb 'List' and resource 'BRREG kunngjøringer' with examples (bankruptcy, mergers, etc.). It clearly identifies the tool's domain (Norwegian company announcements) and distinguishes it from siblings like firmaradar_search_announcements, which is a search tool.

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?

No explicit guidance on when to use this tool versus alternatives such as firmaradar_search_announcements or firmaradar_get_company. The description lists announcement types but does not indicate when this tool is preferred or when other tools should be used.

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