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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which align with the description's 'consulta' (query) nature. The description adds meaningful behavioral context beyond annotations: it is hosted by the platform, requires no platform credentials, is paid via prepaid credit, and involves LGPD responsibility for the client. This enriches transparency, though it doesn't describe response behavior or pagination.

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 opens with the core purpose but contains redundancy: 'consulta em fonte oficial' and 'consulta informação de fontes e órgãos oficiais brasileiros' overlap. The legal and payment context is useful but could be tightened. It is moderately concise with a clear front-loaded purpose, though not as efficient as it could be.

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?

The description covers the tool's source, hosting, credentials, payment model, and legal responsibility, which is helpful for a simple one-parameter tool. However, since there is no output schema, it does not explain what data is returned, and it also lacks input format details, leaving some gaps for an agent.

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 schema has a single required string parameter 'nfce' with no description, and the tool description does not explicitly define its format or expected value (e.g., NFC-e access key, number, or URL). While 'NFC-e' hints at the domain, the description does not compensate for the 0% schema coverage, leaving the agent to guess the exact parameter semantics.

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 'SEFAZ AP: NFC-e, consulta em fonte oficial' and later 'Consulta informação de fontes e órgãos oficiais brasileiros', identifying a query operation on Brazilian NFC-e data. It distinguishes from sibling tools (authenticate, marketplace, etc.) which are generic platform tools, though it could be more specific about the exact NFC-e lookup scope.

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 implies usage context for querying official NFC-e data via SEFAZ AP and provides relevant prerequisites like prepaid credit and lack of platform credentials. However, it does not explicitly state when to use this tool versus alternatives, nor does it include exclusion criteria, so the guidance is only implied.

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