get_business_detail

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read operation by saying 'Obtiene el detalle' and enumerates return fields, but it does not explicitly state this is read-only, mention required permissions, error behavior, or explain how the 'specific company' is selected given that the input schema has no parameters. This leaves significant ambiguity.

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: one sentence listing key return fields, and one sentence giving usage guidance. It is front-loaded with the main purpose and includes no fluff 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?

Although the tool is simple, the description is incomplete for an agent because the input schema has no parameters yet the description implies a specific company. It does not clarify that the business must be selected through some external context or state, nor does it specify output structure beyond the field list. This is a meaningful gap for correct invocation.

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?

There are zero parameters, and schema coverage is 100%, so the baseline is 4. The description doesn't need to explain parameter semantics, though it creates slight confusion by referring to 'una empresa específica' without explaining how the company is identified.

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 action ('Obtiene el detalle de una empresa específica') and lists the specific fields returned (RUT, razón social, giro comercial, etc.). It also differentiates from list_businesses by emphasizing it targets one particular company rather than a list.

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 explicitly says when to use the tool: 'Usar cuando el cliente pregunta por los datos de una empresa en particular.' It provides a clear use context but does not mention alternatives or when not to use it.

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