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

With no annotations, the description carries the full burden and does disclose conditional behavior: with persona it returns only that person's hours, without it returns hours when someone is free. It does not mention authentication, rate limits, or error cases, but the read-only nature is strongly implied by 'consulta' and 'devuelve'.

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?

Three concise sentences front-load the core purpose and date format, then add only the conditional behavior needed to use the persona parameter correctly. 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 3-parameter availability query with an output schema, the description covers all essential call semantics: required business/date, optional person, date format, and expected output behavior. It lacks only explicit handling of invalid businesses or dates and any reference to sibling lookups like listar_negocios, but these are not critical.

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 descriptions are absent, but the description compensates well: it specifies the date format (AAAA-MM-DD), explains the optional persona parameter with a concrete scenario and fallback behavior, and makes negocio's role clear. This goes well 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 names a specific action ('Consulta los horarios libres'), a resource (negocio), and a date, plus an optional filter by person. This clearly distinguishes it from sibling reservation-management tools like consultar_reserva and crear_reserva.

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 clear context for when to call the tool (when free slots are needed) and detailed conditional guidance for the persona parameter. It does not explicitly name sibling alternatives or state when not to use it, but the context is unambiguous.

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