paciente_detalhar

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

No annotations are provided, so the description carries full burden. It states the tool details all information, but does not disclose behavioral traits like permissions, side effects, or limitations (e.g., whether it fetches live data or cached).

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, efficient sentence with no waste. It could be structured to also briefly mention output, but it is sufficiently concise.

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 retrieve-by-ID tool, the description covers the main purpose but lacks detail on what 'todas as informações' includes, especially since there is no output schema. It is minimally adequate.

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 coverage is 100% with parameter 'codigo' already described as 'Código do paciente a detalhar.' The description adds no additional semantic meaning beyond the schema, so a baseline score of 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 'Detalha todas as informações do cadastro de um paciente específico' uses a specific verb (detalha) and resource (paciente específico), clearly distinguishing it from sibling tools like pacientes_listar and pacientes_pesquisar which operate on lists rather than a single patient.

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 usage when needing full details of a specific patient by code, but provides no explicit guidance on when to use this tool versus alternatives, such as pacientes_listar or pacientes_pesquisar.

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