buscar_tabelas_opcoes

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

With no annotations, the description carries the full burden. It discloses key behaviors: default exact match by Name, optional partial search via 'busca_parcial', and filtering by Id. However, it does not mention the return format or pagination details beyond the 'pagina' parameter, which is minor.

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 yet complete, using a single paragraph with numbered observations. Every sentence adds value, and the structure is front-loaded with a clear purpose statement followed by actionable notes.

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 no output schema, the description does not explain return values. However, it provides sufficient context for the intended use case (checking existence before creation) and explains parameter behaviors. It could be slightly more complete about result structure, but it is 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?

The input schema has no descriptions for parameters (0% coverage), so the description fully compensates. Each parameter ('id', 'nome', 'pagina', 'busca_parcial') is explained with its behavior and context, adding significant meaning beyond the raw schema.

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 tool's purpose: 'Buscar tabelas de opções pré-cadastradas no Ploomes CRM.' The verb 'Buscar' plus resource 'tabelas de opções' is specific and distinct from sibling tools like 'salvar_tabela_opcoes' or 'excluir_tabela_opcoes'.

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 provides explicit usage guidance: 'Use para localizar a tabela de opções antes de criar campos do tipo opções pré-cadastradas (TypeId 7) ou itens de checklist.' It also explains the default exact match behavior, when to use 'busca_parcial', and mentions the sibling 'salvar_tabela_opcoes' for context.

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