Get Business Entity Detail via OpenCorporates

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

Discloses source (OpenCorporates), attribution requirement, and output fields (full address, previous names, etc.). No annotations provided, so description carries burden. Missing details on rate limits, failure modes, or data freshness, but provides reasonable expectations.

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, no fluff. First sentence states action and parameters; second sentence adds usage context and output. Every word adds value.

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 no output schema, the description usefully lists output fields. It properly references sibling tool for prior step. Lacks details on error handling or rate limits, but is complete enough for a simple lookup 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 covers all three parameters with descriptions. The description reiterates jurisdiction and company number but adds no new semantics beyond the schema. DryRun parameter is explained only in schema. Baseline 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?

Clearly states the tool looks up one entity by jurisdiction and company number via OpenCorporates, and explicitly distinguishes it from business_entity_search by specifying its use case ('after business_entity_search to get full canonical record').

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 says to use after business_entity_search, providing clear context. Lacks explicit when not to use or alternatives, but the recommendation is strong and sufficient.

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