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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the behavioral detail that only published entries are searched, which is not captured by annotations or schema. However, it does not describe ordering, pagination, or response format.

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 a single, focused sentence that directly communicates the tool's purpose without any superfluous content. It is front-loaded with the verb and resource, making it easy to parse.

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 search tool with annotations and a schema, the description is sufficient to convey purpose and main parameters. It lacks usage differentiation and limit context, but the schema covers technical constraints, and no output schema means return values are not expected. Overall, complete enough for this complexity.

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?

The description explains that search is by text and optional category, directly mapping to the 'query' and 'category' parameters. It does not mention 'limit', but the schema defines its default, min, and max, making it self-explanatory. Given 67% schema coverage, the description adds value for the two primary parameters.

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 the tool searches published VITUR blog entries by text and optional category, using a specific verb ('Busca') and resource ('entradas publicadas del blog de VITUR'). This clearly distinguishes it from sibling tools like vitur-buscar-eventos and vitur-ultimas-noticias.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, usage contexts, or sibling tool distinctions, leaving the agent to infer from the name and description alone.

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