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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds content categories but does not disclose additional behavioral traits such as data source, UK-specific scope, or behavior for missing IDs. No contradiction with annotations exists.

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 a single, front-loaded sentence that efficiently enumerates the key content areas without filler. Every phrase contributes meaningful information about what the tool returns.

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 simple single-ID read tool with rich safety annotations, the description adequately covers the main return categories. It lacks explicit mention of UK scope (present in the annotation title) and not-found behavior, but the low complexity and available annotations make this sufficient.

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 input schema has one required string parameter 'id' with 0% schema description coverage, and the description does not explain what 'id' refers to or how to obtain it. The tool name and phrase 'for a company' imply it is a company identifier, but the description adds no real parameter-level semantics beyond the schema.

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 identifies the resource as a company's registered profile and lists concrete content areas: address, status, SIC, incorporation, and filing/compliance details. It does not explicitly contrast with sibling tools like get_dossier or get_entity, so it stops short of full differentiation.

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 gives no guidance on when to use this tool versus alternatives such as get_dossier, get_entity, or lookup_company. It implies a use case through the phrase 'Registered profile for a company,' but provides no explicit when-to-use or when-not-to-use context.

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