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

No annotations are provided, so the description carries the burden. It usefully discloses that the data comes from an official national source and enumerates the returned fields, but it never states that this is a read-only lookup, says nothing about authentication, rate limits, or behavior on zero results. Solid but incomplete for a tool with zero annotation coverage.

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 tight sentences, front-loaded with the action and source, then query guidance, then return payload. Every sentence earns its place with no redundancy.

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 no output schema, the description correctly fills that gap by listing the return fields (número BDNS, título, fecha, fondos MRR, enlace oficial), and the schema fully covers pagination. Only minor omissions remain, such as behavior for empty result sets or language restrictions on queries.

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%, so the schema already documents q, page and limit (including defaults and bounds), establishing a baseline of 3. The description adds real value by giving sample query strings for q, which the schema's generic 'Texto a buscar' does not supply.

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 (busca) plus resource (convocatorias de subvenciones y ayudas públicas), names the authoritative source (BDNS, fuente oficial) and the geographic scope (España). No siblings exist to disambiguate against, so this is as precise as the tool needs to be.

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?

Gives concrete free-text query examples ('turismo', 'autónomos', 'eficiencia energética', 'Andalucía digitalización') that show the agent exactly how to invoke it. There are no alternatives to exclude, and no prerequisites are stated, so it stops 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.