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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false Picture, so the description adds context about payment per query with pre-paid creditpas, no platform credentials required, and LGPD compliance. It also clarifies the data is not confidential and the client is data controller. This goes beyond annotations to help the agent understand the operational and legal context. No contradiction.

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, two sentences, and front-loaded with the key purpose. The additional legal context is relevant but could be condensed. It earns its place by informing about payment and data responsibility, which are important for agent decision-making.

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 tool is a simple query with one parameter slash no output schema. However, the description lacks details about the expected input format, the output returned, and any limitations (e.g., data availability, rate limits). The context about payment and LGPD is useful but does not compensate for the missing technical guidance. Given the complexity is low, but feedback from parameter semantics is low, overall completeness is insufficient.

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 explain the 'nfce' parameter at all. The parameter name suggests it is the NFC-e identifier, but the description fails to provide format, examples, or how to obtain it. This is a significant gap, forcing the agent to guess the expected input.

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 mentions the tool queries NFC-e Resumida from SEFAZ RS official source. It indicates the purpose but is somewhat vague about what 'resumida' means or what specific operation is performed (e.g., retrieve summary of an NFC-e). It does not clearly distinguish from siblings, but the name and description align enough to give a basic understanding.

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 context about the source and legal aspects but does not specify when to use this tool versus others. It mentions the query is official and not confidential, but no explicit guidance on when to choose this tool over alternatives or when not to use it. The sibling tools like authenticate and connect suggest a setup context, but the description does not clarify integration or prerequisites.

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