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

Annotations already declare this as a read-only, idempotent, open-world, non-destructive operation, so the safety profile is covered. The description adds a genuinely useful behavioral fact beyond that: the payment model (free within a daily allowance, then $0.0005 USDC per call via x402), which affects how aggressively an agent should call it.

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 tight sentences with the record contents front-loaded and pricing second; virtually no filler. The opening fragment 'Full record:' is slightly clipped as a standalone sentence but carries real information density.

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 an output schema present, the description need not document return shape, yet its field enumeration still helps the agent decide relevance at a glance. Annotations cover safety, and the cost model is disclosed; the main missing piece is guidance on when this beats its ror__ siblings.

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% and the single id parameter is documented in the schema with an example format. The description adds no further meaning about the id parameter, so the baseline of 3 applies.

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 enumerates exactly what the tool returns (names/aliases, types, status, founding year, location, website, domains, external ids), which makes it clear this is a full-record lookup keyed by ROR id, matching the title. It does not, however, explicitly contrast itself with siblings like ror__search, ror__relationships, or ror__external-id, so the agent must infer the distinction.

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 statement of when to use this tool versus ror__search (to find an id) or ror__relationships/ror__external-id (for narrower views). The only context offered is the pricing sentence, which informs cost but not tool selection.

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