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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it states the exact price ($0.002 USDC), accepted payment networks via x402, and that failed calls are not charged.

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?

The description is two compact sentences with the purpose and return fields front-loaded, followed by necessary pricing context. The return-field list is slightly redundant given the output schema exists, but the text is largely efficient and contains no 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 simple two-parameter search tool with full schema coverage, annotations, and an output schema, the description is nearly complete. It covers purpose, return fields, public access, and billing behavior; only minor operational details such as pagination or rate limits are absent.

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 the input schema already documents the keyword and result-limit parameters. The description mentions searching 'for a keyword' and lists return fields, but adds no new parameter semantics beyond the schema's own descriptions. Baseline 3 is appropriate when the schema fully carries parameter documentation.

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 search resource: 'EU Funding & Tenders Portal search results (SEDIA) for a keyword,' and lists the returned fields. It is clear what the tool does, but it does not explicitly differentiate itself from sibling tender tools such as gov_ted_eu_procurement or gov_uk_gov_tenders.

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 implies usage by saying it is a 'Public portal search' and that 'the portal indexes calls and tenders,' but it gives no explicit when-to-use or when-not-to-use guidance. No alternative sibling tools are named or contrasted.

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