search_recent_boe

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool searches for documents, without mentioning whether the operation is read-only, what it returns, or any limitations. The lack of detail about side effects or response format leaves an agent unprepared for invoking the tool.

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, clear sentence with no redundant words or filler. It conveys the essential function immediately and is appropriately concise for a straightforward search tool.

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?

Despite having full parameter documentation, the description lacks information about the output format or search behavior. Since there is no output schema and no annotations, the description should at least hint at the expected return value or any usage constraints, but it does not. This makes it minimally viable but incomplete for an agent encountering this tool for the first time.

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?

All four parameters have detailed descriptions in the input schema (100% coverage), so the baseline is 3. The description itself does not elaborate on any parameters beyond what the schema already provides, offering no additional semantic value.

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 uses the verb 'busca' (searches) with the resource 'documentos en el BOE' (BOE documents) and the scope 'últimos días' (recent days). This clearly states the tool's function and differentiates it from sibling search tools that target other data sources.

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 the tool is for searching BOE documents from a recent time window, but does not provide explicit guidance on when to use it over alternatives such as search_auxiliary_data or search_consolidated_legislation. No exclusions or alternative recommendations are offered, so usage context is only implied.

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