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

The description adds no behavioral details beyond what annotations already declare (readOnlyHint, destructiveHint, idempotentHint). It does not mention pagination, ordering, filtering, return format, or any side effects. With annotations present, the bar is lower, but the description still fails to provide any extra context.

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 extremely concise (one sentence) and front-loaded, which is good. However, it is under-specified to the point of being unhelpful. It earns a middling score because conciseness without substance is not effective.

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?

With two parameters, no output schema, and no parameter descriptions, the tool is severely under-documented. An agent cannot determine how to use 'query' or 'account', nor what the response will contain. The description fails to cover even basic usage context.

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 description does not explain the 'query' and 'account' parameters at all. Schema description coverage is 0%, so the agent has no clue what these parameters control (e.g., search filters, account scoping). This is a critical gap for usability.

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 the action ('Listar') and the resource ('Notas Fiscais de Serviços') with the HTTP method and path. It distinguishes from sibling tools like _get, _create, etc., by implying a collection-level operation. However, it does not explicitly mention scope (e.g., all vs. filtered), which is a minor gap.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., _get for single item, or _create for new records). The purpose is implied by the name but not elaborated. There is no mention of typical use cases or exclusions.

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