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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful context about the return format (JSON-LD linked-data record with parties, legal basis, court, full text), going beyond annotation basics. Minor gap: no mention of error conditions or auth, but annotations lower the bar.

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 with the purpose front-loaded. The first sentence states the action, the second describes the return value and prerequisite workflow. No wasted words.

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?

The tool is simple (one parameter) with rich annotations, an output schema, and a clear workflow instruction. The description covers purpose, return content, and how to obtain the required ID, making it complete for an agent to invoke correctly.

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% for the single parameter, and the schema description already explains notice_id as the numeric Gazette notice ID returned by gazette_insolvency. The description's mention of 'numeric notice ID' adds little beyond the schema, so the baseline 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 the tool fetches the full legal wording of a Gazette notice by numeric notice ID, with a specific verb and resource. It distinguishes itself from the sibling gazette_insolvency tool by focusing on full text vs. listing, and mentions the linked-data record content.

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?

Explicitly instructs to use gazette_insolvency first to find notice_numeric_id values, providing clear workflow guidance and effectively differentiating this tool from its sibling listing tool. This is a direct when-to-use instruction.

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