buscar_opcoes_tabela

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

With no annotations provided, the description must disclose behavioral traits. It lacks information about pagination (pagina parameter), optional filtering (nome), side effects, and return format. The description does not clarify that the tool is read-only or how results are paginated.

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 concise but too brief. It is front-loaded with the purpose but omits important details about parameters and usage, making it less helpful despite its brevity.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is incomplete. It should explain all parameters and expected output. The current version only covers the required parameter.

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 0%, so the description should compensate. It only mentions tabela_id, leaving the nome and pagina parameters completely unexplained. The agent has no guidance on how to use these optional parameters.

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 verb 'buscar' and the resource 'opcoes de uma tabela de opcoes' in the context of Ploomes CRM. It identifies the required filter (tabela_id). However, it does not differentiate from the similarly named sibling 'buscar_opcoes_tabela_opcoes', which could cause confusion.

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?

No usage guidance is provided. The description only states a requirement (inform tabela_id) but does not indicate when to use this tool over alternatives like 'buscar_opcoes_tabela_opcoes' or 'buscar_tabelas_opcoes'.

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