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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond the annotations: the underlying data source (OpenAIRE Graph API), that it is an EU-funded open science infrastructure, and that no auth is required. It also lists the returned project fields. No contradiction with 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?

Two well-structured sentences: the first states purpose with examples, the second lists return fields and adds data-source/auth context. Everything is front-loaded, there is no filler, and every sentence earns its place.

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 simple search tool with a fully described schema, an output schema, and safety annotations, the description covers all needed context: what it searches, what it returns, the data source, and auth requirements. Pagination is covered by the schema's page/page_size descriptions, so nothing essential 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 page, query, and page_size are already fully documented with descriptions, defaults, and constraints. The description's examples ('renewable energy', 'H2020') reinforce the query parameter but do not add new semantics beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb ('Search'), a specific resource ('OpenAIRE funded research projects'), the search mode (free-text across title, acronym, keywords), and gives concrete examples. It also enumerates the returned fields, making it unmistakable what this tool does. The resource type 'projects' distinguishes it from sibling tools for organizations and products.

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 gives clear context: it searches research projects, and the resource type is unambiguous. However, it does not explicitly tell the agent when to prefer this tool over openaire.organizations.search or openaire.products.search, nor does it state any exclusions. The distinction is inferable from the resource name rather than stated.

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