consultar_cest

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

No annotations provided, so description carries full burden. It discloses offline behavior, bundled SQLite, and a warning about sample data with instructions to populate. However, it does not specify what happens if the CEST is not found.

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 and well-structured with explicit sections (Purpose, Quando usar, Comportamento offline, AVISO, Formato). No superfluous information.

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?

Output schema exists, reducing need for return value explanation. Covers purpose, usage, offline behavior, and parameter format. It lacks details on error handling or empty results, but is otherwise complete.

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 a clear description, but the description adds format details (7 digits, with/without punctuation) and examples, enhancing usability beyond 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 function: 'Consulta o Código Especificador da Substituição Tributária (CEST)' and its purpose to identify products subject to ICMS-ST. It is distinct from sibling tools that deal with other tax codes.

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?

Explicitly states 'Quando usar: ao emitir NF-e com produtos sujeitos ao ICMS-ST,' providing direct context. It does not mention when not to use or alternatives, but the sibling list suggests no overlap.

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