buscar_noticias

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

No annotations are provided, so the description carries the full burden. It does add 'Read-only' as a safety indication, which is useful, but it does not describe the return format, pagination, or any side effects. The behavioral disclosure is minimal.

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 sentence plus 'Read-only.' It is extremely concise, front-loaded with the main purpose, and contains no unnecessary 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?

The tool is simple (one parameter, no output schema), and the description covers the basic purpose and read-only nature. However, it lacks parameter semantics and any indication of output structure or examples. The condition about the municipality's public API adds some context, but overall it is only minimally complete.

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 input schema has one parameter 'consulta' with no description, and schema description coverage is 0%. The description does not explain what this parameter means or how to use it, only that the tool searches for news. The parameter name offers some inference (query), but explicit semantics are missing.

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 clearly states 'Buscar noticias oficiales' (search official news), which is a specific verb+resource combination. This distinguishes it from sibling tools like consulta_ciudadana or buscar_fuentes, which serve different purposes.

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?

Provides a clear usage condition: 'cuando el municipio expone API pública' (when the municipality exposes a public API). However, it does not explicitly mention alternatives or when not to use this tool, so it lacks some exclusion guidance.

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