boe_search

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

No annotations are provided, so the description carries full responsibility. It mentions relaxed search but does not disclose read-only status, authentication needs, rate limits, or error behavior. For a search tool, this is insufficient.

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 very concise: two sentences with no unnecessary words. It front-loads the primary purpose and adds key detail about relaxed search in the second sentence. Highly efficient.

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?

Given no output schema or annotations, the description should provide more context about return format, error handling, and usage scenarios. It explains a key feature but leaves out essential completeness for practical use.

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?

Schema coverage is 100%, so baseline is 3. The description adds the nuance of relaxed search behavior for the 'q' parameter but does not explain 'limit' usage beyond its schema description. No additional meaning beyond schema.

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 searches consolidated legislation in the BOE (Spanish Official State Gazette). It distinguishes from siblings like boe_get_article and boe_search_recent_summaries by focusing on normative search and mentioning relaxed search capability.

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 when to use: for searching consolidated legislation, with a fallback to relaxed search if exact terms fail. However, it does not explicitly mention when not to use this tool versus siblings like boe_search_recent_summaries, providing only implicit guidance.

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