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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a meaningful access constraint (10-K names require Pro) and details what data comes back, but says nothing about pagination behavior or how maxResults/company-part grouping affects results, which are relevant for a read tool. A 3 reflects moderate added value over the annotations.

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 front-loads verb+resource, which is good, but the entire content is a single run-on sentence cramming return fields, examples, and plan gating together. Every clause is relevant, yet the lack of sentence breaks makes it harder to parse than necessary.

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?

With no output schema, the description carries the burden of describing returns, and it does so thoroughly (kind, country, LEI, parent/parts, verbatim 10-K sentence, 12-month contract value). Combined with annotations covering safety, an agent has most of what it needs; only pagination/result-shaping guidance is missing.

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 100%, so both parameters are already documented, giving a baseline of 3. The description reinforces subject matter (organizations, 10-K mention names) but adds no new syntax, format, or usage detail beyond the schema's slug/name and maxResults semantics.

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?

States a specific verb+resource ("Get an organization") and scopes it precisely to entities no market we cover lists, which cleanly separates it from listed-company tools. It also enumerates the returned facets (kind, country, LEI, parent/parts, 10-K mentions, contract value), so the purpose is concrete. The dense phrasing slightly muddies the core intent, 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?

It implies when to use it by describing the target population (U.S. Government, federal agencies, unlisted companies) and notes a Pro-plan prerequisite for 10-K-derived names. However, it names no alternative sibling tools and gives no explicit when-not guidance, so selection against tools like SearchInstitutions or GetGovernmentContracts is left to inference.

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