get_borme_summary

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions the high-level function and does not reveal details such as pagination, filtering capabilities, output format, or whether it represents a read-only operation. This is insufficient for a tool with multiple configurable options.

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, concise sentence that front-loads the core purpose. However, it omits any mention of the tool's configurable options (max_items, province_filter, include_pdf_links), making it slightly under-informative for the tool's actual complexity.

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 four parameters, no output schema, and no annotations, the description fails to convey the tool's full capabilities. It only mentions the date-based summary, ignoring the filtering, limiting, and PDF link features that the schema documents. This leaves significant gaps for an agent deciding how to invoke the tool effectively.

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 100% description coverage for all four parameters, including format for date, constraints for max_items, and purpose for province_filter and include_pdf_links. The description adds no additional semantic value beyond the schema, matching the baseline for high schema coverage.

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 the tool retrieves the BORME summary for a specific date ('Obtiene el sumario del BORME para una fecha específica'), using a specific verb and resource. It differentiates from siblings like get_boe_summary_range by emphasizing a single date, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus siblings such as get_boe_summary_range, get_weekly_summary, or get_boe_summary. The description merely states what it does without indicating appropriate use cases or exclusions.

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