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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description's added value is the sequencing hint and the mention of budget/partner/output details, which is modest and partly 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 sentence with the action, the identifier, and the workflow trigger front-loaded. No filler and nothing that could be cut without losing meaning.

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, full annotations, and a fully documented single parameter, the description needs only to explain purpose and sequencing, which it does. Return values need not be described, though the brief parenthetical about budget/partners/outputs is a helpful preview rather than a burden.

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% with a single required 'id' parameter and a concrete example value, so the schema carries the parameter documentation. The description adds only the provenance hint that the ID comes from a prior search, which is mildly useful but not additional syntax or format guidance.

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 and resource ('Fetch a funded research project') plus the identifier type ('by OpenAIRE ID'), which clearly separates it from the sibling search tools. The only weakness is the slightly loose sibling reference ('search_projects' vs. openaire_search_projects), which is still unambiguous in context.

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?

'use after `search_projects`' gives a concrete trigger condition and implies the search-then-fetch workflow, so an agent knows when this tool is the right call. There are no explicit exclusions or when-not rules, which keeps it short of a 5.

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