agenda_horarios_livres

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

No annotations are provided, so the description must fully disclose behavior. It states it searches for free slots, but does not explain how 'free' is determined (e.g., ignores non-working hours? conflicts with existing appointments?), any restrictions (e.g., only future dates?), permissions required, or response format. The description is too brief for a mutating-like search operation.

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 a single, concise sentence that efficiently conveys the primary purpose. It is front-loaded with the verb and resource, with no superfluous words.

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 5 parameters, no output schema, and no annotations. The description only gives a high-level purpose. It lacks details about the return format (list of time slots? duration? date-time? sorted?), pagination, error handling, or constraints like maximum date range. For a search tool with moderate complexity, this is insufficient.

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 description coverage is 100%, so the schema already documents all 5 parameters. The description adds no additional meaning beyond the schema, e.g., does not clarify how 'duracao' affects the free slot search or the interaction between 'localProDoctorId' and free slots. Baseline 3 is appropriate.

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 ('Busca por' - search for) and the resource ('horários livres na agenda de um usuário em um período determinado' - free time slots in a user's schedule over a given period). It effectively distinguishes from siblings like agenda_listar_agendamentos which list actual appointments, not free slots.

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 the tool is used when free slots are needed, but it does not explicitly state when to use it or when to use alternatives (e.g., for booking, use agenda_inserir_agendamento). No 'when not to use' or context about prerequisites is provided.

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