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

Annotations already establish a safe, non-destructive, closed-domain read. The description adds genuinely new behavioral context: 'Not all documents have extracted text available' (a partial-failure caveat an agent must anticipate) and the attribution/licence obligation when reusing content. It stops short of saying whether absent text yields an error or an empty result.

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?

Front-loaded with purpose, then the workflow, then the caveat, then licensing. Slightly padded by the licensing paragraph and stray double-backtick artifacts (``url``), but each section carries actionable information for a retrieval tool whose output must be cited.

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?

An output schema exists, so return-value shape needn't be restated. The description covers the key gaps an agent needs — the search-first workflow, accepted input forms, possible missing text, and attribution requirements. Only the failure mode when text is unavailable is left unstated.

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% and the property description already enumerates the accepted input forms, so the schema does the heavy lifting. The description's mention that URLs, paths and bare filenames are accepted and that the search result's url can be passed directly reinforces the linkage to the search tool, but adds little beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('Get the full text of a specific Revenue Tax & Duty Manual document'), and distinguishes itself from the sibling search tool that only finds documents. An agent can tell exactly what this returns without opening the schema.

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 prescribes the workflow: 'Use search_revenue_documents first to find the document' and explains that the search result's url can be passed straight through. This is a clear prerequisite plus the alternative to use upstream, leaving nothing to inference.

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