list_businesses

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

No annotations are provided, so the description carries the behavioral burden. 'Lista' and 'Retorna' imply a read-only operation, and the description discloses exactly what information is returned. It does not discuss auth or pagination, but for a zero-parameter list operation these are minor gaps.

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?

Two short sentences convey the purpose, the return contents, and the exact user scenario in which the tool should be used. There is no filler or repetition.

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, zero-parameter list tool without an output schema, the description is complete: it names the resource, the data returned, and the triggering use case. An agent has enough information to select and invoke it correctly.

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 tool has zero parametersaineisto, and the rubric assigns a baseline of 4 for no-parameter tools. The description adds relevant information about the output fields, so no parameter documentation is missing.

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 starts with a specific action and resource: 'Lista todas las empresas registradas del usuario.' It names the returned fields (RUT, razón social, giro, estado, certificado digital), so an agent can clearly distinguish it from siblings like get_business_detail or get_user_info.

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 gives an explicit trigger: 'Usar cuando el cliente pregunta cuántas empresas tiene o cuáles son.' It could also mention when not to use it or point to get_business_detail for a single company, but the stated usage context is clear enough.

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