Search Gazette Corporate Insolvency Notices

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by stating it is the official UK public record, that notices are legally effective, and that results are sorted by severity. 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?

Six sentences with no wasted words. The most important information is front-loaded: purpose, supported notice codes, sorting, and how to use results. 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 7 params, zero required, full schema coverage, and an output schema (not shown but present), the description adds sufficient context: data source, sorting, and follow-up action. It is complete enough for an AI agent to understand the tool's role and usage.

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 description does not need to repeat parameter details. It adds context about using the result's notice_numeric_id to read full wording, which is beneficial but not parameter-specific. 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 clearly states it searches The Gazette's insolvency notice index by entity name, specifies the notice codes covered, and mentions severity sorting. It distinguishes from sibling tools by focusing specifically on corporate insolvency notices, and references the notice:// resource for full wording, implying the separate gazette_notice 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?

Provides clear context on when to use (searching corporate insolvency notices) and mentions sorting by severity. It also guides how to access full legal wording via notice_numeric_id. However, it does not explicitly state when not to use or compare with alternatives like company_search or gazette_notice.

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