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

No annotations are supplied, so the description carries the full burden. "Cerca" makes the read-only nature implicit and "già finanziati" tells the agent the data is historical/awarded rather than open calls, but there is no statement on data freshness, coverage limits, or result ordering.

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?

Purpose and use cases are front-loaded in two sentences, followed by a compact Args list. Minimal waste, though "(CORDIS Intelligence)" is a branding tag that adds little for an agent.

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, return values need not be explained, and the description covers purpose, use cases, and all four parameters. The remaining gap is sibling differentiation and the behavior of nullable filters, which is meaningful but not fatal for a zero-required-param search tool.

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 0%, so the Args block does real work: it explains each of the four parameters, including the semantic intent of query ("parola chiave tecnologica"), the SME/startup meaning of only_sme, and Italian-city examples for city plus the default for limit. It does not clarify that all parameters are optional/nullable or what happens when query is omitted, which prevents a 5.

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 ("Cerca") and resource ("progetti Horizon Europe già finanziati dall'UE con partecipanti italiani"), scoped further to CORDIS. An agent can tell it is a funded-project search rather than a call search, but the description never names the sibling it differs from (search_bandi, get_cordis_stats, get_cordis_project_consortium).

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?

Offers use cases ("benchmark competitivo, studio degli abstract vincenti e partner search") which give implied context for when to reach for it. However there are no exclusions and no routing to alternatives, which matters here because search_bandi (open calls) and get_cordis_project_consortium (consortium detail) overlap conceptually with this tool.

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