dataprem_borme_search

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

With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only search operation via verbs like 'busca' and 'localizar', but it does not disclose output format, pagination, error behavior, or any side effects. The description adds some context (act types, date range) but lacks richer behavioral traits.

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 and well-structured: a clear opening sentence stating the purpose, followed by a compact, tagged parameter list. Every sentence contributes value, and there is no redundancy or extraneous detail.

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 has a simple 3-parameter schema and an output schema is present, so the description need not explain return values. However, it leaves minor gaps, such as whether company_name searching is exact or partial and whether date ranges are inclusive. Overall, it is largely complete for a basic search tool.

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 description compensates for the 0% schema coverage by providing an Args section that explains each parameter: company_name (nombre o razón social), date_from (formato YYYY-MM-DD, opcional), and date_to (formato YYYY-MM-DD, opcional). This fully documents all three parameters, adding meaning beyond the bare 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's function: 'Busca actos registrales en el BORME' (searches registry acts in the BORME), and it lists specific act types (constitución, nombramientos, ceses, ampliaciones de capital). This specific verb+resource pair distinguishes it from sibling tools like catastro, cendoj, and tenders, which target different 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 provides clear context: it is used to find commercial registry acts for a company, with optional date range filtering. It does not explicitly mention exclusions or alternatives, but the distinct domain (BORME) compared to siblings (catastro, cendoj, tenders) makes the usage context clear, though not explicitly contrasted.

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