consultar_ncm

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

No annotations provided, so description carries full burden. Discloses offline behavior (reads from bundled SQLite, no connection needed), warns of limited sample (~10,515 records), and provides guidance to populate full table. Also specifies parameter format. Good transparency for a query tool.

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?

Description is efficient, covering purpose, usage, behavior, and parameter format in a few sentences. Front-loaded with key info. Slightly wordy with 'AVISO' but earned.

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 output schema exists and tool is simple, description covers usage scenarios, offline capability, database limitation, and format. No missing critical context for a NCM lookup tool.

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 already described. Description adds example formats and database limitation context but does not significantly enhance meaning beyond schema. Baseline of 3 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?

Description uses specific verb 'consulta' and resource 'Nomenclatura Comum do Mercosul (NCM)' and clearly states purpose: identificar classificação fiscal para NF-e, IPI, SPED. Distinct from many sibling consultar_* tools.

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?

Explicit when-to-use scenarios provided: ao emitir nota fiscal, importação/exportação, cálculo de tributos. No explicit when-not-to-use but context is clear. Does not name alternative tools for similar tasks.

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