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

Annotations already signal read-only, idempotent, non-destructive behavior. The description goes beyond annotations by specifying the returned fields (id, legal name, short name, alternative names, website, country) and the API provenance, which helps an agent anticipate output and source. No additional behavior like pagination or rate limits is disclosed, but these are partially covered by the 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?

Three sentences, each with a distinct purpose: what the tool does, what it returns, and the data source/auth requirement. It is front-loaded with the action and avoids 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?

For a 3-parameter read-only search with an output schema, the description covers purpose, return content, and source. It doesn't explicitly discuss pagination, but that is handled by schema defaults and descriptions. It is slightly thin on when the query parameter is optional, but the schema already marks no required parameters.

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?

Parameter descriptions in the schema cover all three parameters (query, page, page_size), so the baseline is 3. The description repeats the query examples but adds no additional parameter semantics such as accepted formats or edge cases.

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 the specific action ('Search OpenAIRE'), the resource ('research organizations'), and the matching behavior by name, with concrete examples. It does not explicitly name any sibling tool or contrast itself with similar registries like ror.organizations.search, so it stops short of full differentiation.

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 description establishes a clear context—searching OpenAIRE's organization registry via the Graph API—and explicitly states no auth is required. However, it does not state when to prefer this over similar organization registries or provide exclusions.

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