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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond those: payment required per query (prepaid credit), authentication is not via platform credentials but via specific credentials, data is not confidential, and the customer is the data controller responsible for LGPD compliance. 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 is three sentences and front-loaded with the tool's core purpose ('Imprimir, consulta em fonte oficial'). Each sentence adds distinct value: purpose, payment/auth conditions, and legal responsibility. It is efficient, though slightly informal in structure, with no wasted words.

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 six required parameters, no output schema, and zero parameter descriptions, the description must carry a heavier operational burden, but it only provides high-level context. It fails to specify the query result format, parameter semantics, error conditions, or credit-related failure behavior. An agent cannot reliably invoke this tool solely from the description.

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 any of the six required parameters. 'placa', 'renavam', 'login_cpf', and 'login_senha' are relatively self-explanatory, but 'a3' and 'a3_pin' are cryptic digital-certificate terms, and no formats, constraints, or examples are provided. The description completely fails to compensate for the absent schema descriptions.

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 identifies the specific resource (ECRVSP ATPV Intenção de Venda) and the action ('Imprimir, consulta em fonte oficial'), stating it queries official Brazilian sources. Sibling tools are unrelated platform utilities, so there is no real differentiation burden. A small deduction for not making the output/return nature explicit beyond 'imprimir'.

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 context: hosted by the platform, no platform credentials, paid per query with prepaid credit, and LGPD responsibility. This implies use cases where official ATPV data is needed, but it never explicitly contrasts with alternatives or states when not to use the tool, so guidance remains implied rather than explicit.

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