Texto de una disposición del BOE

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that it returns plain text, which is useful, but does not mention rate limits, truncation behavior, or what happens for large documents.

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 efficient sentence that front-loads the verb and resource. It is appropriately sized and wastes no words.

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 tool that can return large documents (max 50,000 characters) with no output schema, the description should explain return format, truncation, or size limits. Combined with incomplete parameter documentation, it leaves the agent guessing about the output.

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 50%. The description explains the 'id' parameter format with an example, but gives no information about 'max_caracteres' — its purpose, default, or truncation behavior — leaving a significant gap.

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 (Devuelve) and resource (texto plano de una publicación del BOE) and identifies the input type. It explicitly names boe_sumario_dia and boe_buscar as the sources of the identifier, distinguishing it from those siblings.

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 context by telling the agent where the required identifier comes from (boe_sumario_dia or boe_buscar), which routes the agent correctly. However, it does not state when not to use this tool or what happens with invalid identifiers.

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