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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, so the safety profile is covered. The description adds that it joins multiple sources and surfaces 'the three things most worth knowing first', which is useful read-behavior context, but it says nothing about latency, rate limits, or what happens when a name resolves to multiple companies beyond 'resolved to one company'.

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?

It is a dense but front-loaded enumeration, opening with the core purpose and then listing coverage. Every clause names a real dataset, so little is wasted, though the long trailing list of data categories is close to padding for a single-parameter read.

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?

For a broad aggregate read tool with annotations covering safety and no output schema, the description needs to tell the agent what it will and won't get back. It names the coverage areas but not the shape of the response, so an agent can't tell what 'joined and read' actually returns. Adequate but incomplete.

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 single parameter's description already explains number-vs-name resolution. The tool description itself adds nothing about the parameter, but with full schema coverage the baseline of 3 is exceeded slightly because the 'resolved to one company, named in the reply' behavior implies a resolution step the caller should be aware of.

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 specifies a broad 'public record' lookup for a UK company and enumerates the datasets it joins (registry facts, distress signals, director/PSC verification, payment practices, contracts, gender pay gap, Environment Agency registrations, Sanctions List). The verb+resource is clear, but the tool heavily overlaps with many siblings (distress_signals, contracts_won, gender_pay_gap, payment_practices) without stating how it differs from them, keeping it short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance. Given 19 siblings that each cover a slice of this tool's outputs, the absence of any routing advice is a real gap — an agent can't tell whether to call this aggregate tool or the targeted siblings.

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