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

Annotations already declare read-only, idempotent, open-world behavior, yet the description adds real value beyond them: results are bounded, includes source hashes and CC0 attribution, and explicitly 'without issuing an identity verdict' — a meaningful caveat about how much the result should be trusted for identity matching. It does not mention rate limits or how scoring/flags should be interpreted.

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: the first front-loads capabilities, the second front-loads the return contract and the identity caveat. Wording is dense and jargon-heavy ('source hashes', 'bounded institution names') but no sentence is filler.

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?

An output schema exists, so the description needn't explain return shapes, yet it spends space on returns while leaving two of four parameters (max_results, country_code) undiscussed at 25% schema coverage. For a multi-mode tool with mode-dependent constraints, the description is 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 description coverage is only 25%, and the description compensates partially by explaining what the query means in each mode (name, ROR ID, affiliation). It adds nothing about max_results (1–20, default 10) or the country_code restriction that is forced to null for id/affiliation modes, which the agent can only learn from the JSON schema's conditionals.

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?

Specific verb+resource (search ROR organization metadata) with the three supported modes (name search, exact ID resolution, affiliation matching) spelled out, so an agent can map the description onto match_mode without opening the schema. It does not differentiate against sibling organization lookups (wikidata-organization-search, organization-evidence, lei-entity-search), so it stops 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?

The three modes are named, implying when each applies (free-text name, exact ID, affiliation string), but there is no explicit 'use this when… instead of X' guidance and no prerequisites. With many overlapping organization/entity-research siblings, routing remains inferential.

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