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

No annotations are provided, so the description carries the full burden. It does disclose a read-style 'search' behavior and a worldwide scope, but it does not mention output volume, pagination, rate limits, or whether q expects a company name, registration number, or jurisdiction. The lack of any mutation claim is useful, but more behavioral context would help.

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 definition is a single short sentence with no wasted words, and the service name and core purpose are front-loaded. Its brevity is efficient, although some of the shortness reflects missing behavioral and parameter detail rather than polished concision.

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 one-parameter search tool with an output schema, the description is minimally adequate to select and invoke the tool. However, the lack of q guidance and the absence of any annotation-level safety context leaves an agent guessing about what to pass, making it complete only at the basic viable level.

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 description coverage is 0%, so the description must compensate, but it never mentions q explicitly. The phrase 'company registrations search' lets an agent infer that q is likely a search term, but the expected format, accepted values, and behavior of the default empty string are undocumented.

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 identifies a specific resource (OpenCorporates company registrations) and an action ('search'), and adds a 'worldwide' scope that helps differentiate it from jurisdiction-specific tools. It is clear enough for an agent to know what domain the tool operates in, though it stops short of a full imperative statement.

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 guidance on when to use opencorp versus alternatives such as orgname, gleif_name, or lei, despite a large sibling list. No exclusions, prerequisites, or example scenarios are provided; the only usage signal is implied by the name and one-line description.

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