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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description need not repeat safety. The description adds transparency about data access: it's the same data available to citizens, not confidential, and the client is responsible (LGPD). It also clarifies that payment is via prepaid creditchers, which is important for cost expectations. No mention of output format, but for a simple read operation, this is adequate.

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 four sentences, all providing relevant context (domain, payment, legal). It's not excessively long, and it's structured as: what it is, how to use it (payment), and data governance. It could be more concise, but it avoids fluff. The front-loading is acceptable with the main purpose stated first.

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 operational aspects (payment, credentials) and legal compliance (LGPD) which are useful, but it does not mention the response format or potential errors (e.g., invalid key, network failures). For a query tool with no output schema, this is a notable gap. It also doesn't mention any alternative tools for similar queries, though no sibling seems directly related.

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 one parameter 'chave' with no description, and the tool description does not explain what 'chave' means (likely the NFS-e access key or number). Since schema coverage is 0%, the description does nothing to clarify the parameter. However, the domain context (NFS-e query) gives a strong hint that 'chave' is the service key, so it's not completely opaque, but still a gap.

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 it's a query (consulta) for NFS-e (Nota Fiscal de Serviços) in Farroupilha, RS, Brazil, and that it uses official sources. It doesn't explicitly name the tool's verb but 'consulta' implies retrieval, and the title includes 'consultar' (query). It identifies the domain (NFS-e) and the context (official Brazilian source).

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 gives operational guidance: it mentions prepaid credits, no platform credentials, and client responsibility under LGPD. However, it does not explain when to use this tool compared to alternatives, nor does it specify any particular prerequisites beyond having a 'chave' (key). The absence of usage examples or typical failure reasons leaves some ambiguity.

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