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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is fully covered by structured data. The description adds useful payload semantics — validated equivalents grouped by language with reliability rating, context, usage note and source — but says nothing about pagination, rate limits, credential requirements, or behavior when lang_code filters the record, and some of the return detail is duplicative of the output schema.

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?

A single dense sentence front-loads the action and the returned content, followed by an example call. The inline example is slightly redundant given the input schema already carries an examples array, but nothing else is wasted.

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 single-record lookup with a full output schema and complete annotation coverage, the description supplies what an agent needs: the id source, the record's shape, and the fact that equivalents are validated and language-grouped. The only missing piece is what happens when lang_code is supplied versus omitted.

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 coverage is 100%, so every parameter including concept_id origin and lang_code's ISO 639-1 value list is already documented in the schema. The description's note that concept_id comes from pearl_search_terms restates the schema description rather than adding new meaning, and lang_code is not mentioned at all in the description. Baseline 3 is appropriate.

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 ('Retrieve') and resource ('full WIPO Pearl database record') scoped to exactly one concept_id. It also implicitly separates itself from the sibling pearl_search_terms by identifying that tool as the source of the id, so an agent can pick between search and fetch without opening a schema.

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?

Clearly establishes the workflow dependency: concept_id comes from pearl_search_terms, which tells the agent to search first and fetch second. There is no explicit when-not-to-use statement or discussion of overriding with lang_code, but the usage context is unambiguous.

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