procedimentos_pesquisar

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

No annotations provided, so description carries full burden. Discloses fallback behavior if API does not support filters, which is critical for correct invocation. However, does not mention other behaviors like pagination, ordering, or authentication.

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?

Two sentences, front-loaded with purpose, no wasted words. Efficient and clear for an agent.

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?

No output schema; description does not explain return format (e.g., list of procedures with fields). Missing context on error behavior. For a search tool with no output schema, more detail needed.

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%, baseline is 3. Description mentions 'nome/código' corresponding to parameters but adds no additional semantic detail beyond the schema, such as how filters combine (AND/OR).

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?

Describes searching medical procedures from a table, using specific verb 'pesquisa' and resource 'procedimentos médicos de uma tabela'. Clearly distinguishes from sibling tools like 'procedimento_detalhar' (detail) and 'tabelas_procedimentos_listar' (list tables).

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?

Implied usage for searching/filtering procedures, but lacks explicit guidance on when to use this vs alternatives like 'procedimento_detalhar' or 'tabelas_procedimentos_listar'. Does not mention when not to use.

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