agenda_buscar_agendamentos_paciente

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

No annotations are provided, so the description carries the full burden. It describes a read operation ('busca') but does not explicitly confirm read-only behavior, required permissions, rate limits, or any side effects. This leaves the agent uncertain about safety and constraints.

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 conveys the core functionality without waste. It is front-loaded with the main purpose, though it could be slightly expanded to include return value hints.

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 no output schema, so the description should explain what is returned. It does not, leaving a gap. Given 4 parameters including optional date filters, the description is too brief to fully guide an agent on expected results or edge cases.

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?

Parameter schema coverage is 100%, so the schema already documents all parameters and their formats. The description adds no additional meaning beyond the schema, meeting the baseline for a tool with full schema coverage.

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?

Description states 'Busca os agendamentos de um paciente específico num período' which clearly specifies the action (busca), resource (agendamentos), and constraints (paciente específico, período). This distinguishes it from sibling tools like agenda_listar_agendamentos (list all) and agenda_buscar_por_status_tipo (search by status/type).

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?

Description implies the tool is used to find appointments for a specific patient within a date range, which provides clear context. However, it does not explicitly state when to use this over alternatives, nor does it mention 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.