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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context about data being the same available to citizens, not confidential, requiring prepaid credit, and carrying LGPD data-controller responsibility. No contradiction with annotations.

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 contains redundant legal and platform boilerplate, such as repeated references to official sources and LGPD responsibilities, which could be condensed. Important operational information like the parameter is missing, so the length is not justified by content value.

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?

Despite low complexity (one parameter and no nested objects), the description omits essential parameter guidance and return value expectations. It covers payment, credential, and legal context, but not enough to fully support correct invocation.

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 description coverage is 0%, and the description does not mention the required 'codigo_autenticidade' parameter at all. It does not explain where the code comes from, its format, or how it should be supplied, leaving the agent without sufficient information to invoke the tool correctly.

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 identifies the tool as a query/consulta for NFS-e (Nota Fiscal Eletrônica de Serviços) from Prefeitura SP Sumaré, using a specific verb and resource. This distinguishes it from the generic sibling platform tools like authenticate, connect, and marketplace.

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 clear operational context: it is an official-source query, requires no platform credentials, and is paid per query with prepaid credit. It does not name alternative tools or explicitly state when not to use it, but the use case is clearly implied and no conflicting alternative is present.

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