boe_search_recent_summaries

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

The description mentions 'exhaustively' but provides no details on return format, pagination, rate limits, or side effects. Since annotations are absent, more behavioral context would be beneficial.

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 concise—only two sentences—with the main action in the first sentence and additional context in the second, containing no superfluous information.

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 tool with two parameters and no output schema, the description covers the core purpose and scope adequately, though it omits details on result format or limitations.

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?

With 100% schema coverage, the description adds no extra meaning to the parameters; the schema already documents 'days' and 'keyword' adequately, so a baseline score of 3 is appropriate.

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 specifies the action (thoroughly scans), resource (summaries of the last N days), and scope (searching for keywords), distinguishing it from siblings like 'boe_search' which likely searches all documents.

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?

It indicates usefulness for finding hidden announcements ('Útil para encontrar anuncios ocultos') but does not explicitly state when to use this tool versus alternatives like 'boe_search' or when not to use it.

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