Fetch Full Record from UK Due Diligence Register

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

Beyond annotations (readOnly, etc.), the description adds valuable context: routing behavior by prefix and what each route returns (full profile, record, legal text). This enhances understanding of the tool's behavior.

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?

The description is concise: a single header sentence followed by a clear bullet list. No redundant information, effectively front-loading the key action.

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 a single parameter, output schema, and annotations, the description thoroughly covers the tool's purpose and routing. It could optionally clarify differences from specific profile siblings, but overall it's complete.

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?

The schema already documents the parameter format. The description adds the routing mapping from prefix to register, which is not in the schema, providing additional semantic value beyond the 100% coverage.

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 fetches full records for IDs from search and details routing by prefix. It distinguishes from siblings by being a generic fetch tool, though it does not explicitly differentiate from specific profile tools like company_profile.

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?

The description implies use after search to get full records, but does not explicitly state when not to use this tool or provide alternatives. No exclusion or comparison with sibling tools is given.

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