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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds valuable context: payment per query with prepaid credit, no platform credentials needed, data is not confidential, and LGPD responsibilities. This goes beyond the annotations without contradicting them.

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 (three sentences), front-loaded with purpose, and each sentence contributes meaningful information about hosting, payment, data source, and legal compliance. No fluff or redundancy.

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?

Given 7 parameters, no output schema, and no parameter explanations, the description is incomplete. It does not clarify the role of optional credentials, what the query returns, or how payment is processed beyond 'prepaid credit'. An agent would struggle to correctly invoke this tool without additional info.

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 provides no explanation of any of the 7 parameters. It does not mention chave_infracao, placa, or the credential fields (login_cpf, pkcs12_cert, etc.), leaving the agent without guidance on how to populate them 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 states the tool queries 'Penalidade de Advertência por Escrito' (written warning penalty) from SENATRAN official sources. The verb 'consulta' and specific resource distinguish it from the generic sibling tools like authenticate or report_bug.

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?

Usage context is implied by the name and description (query official SENATRAN penalty data), but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description mentions 'sem credenciais da plataforma' but does not clarify when to provide the optional credential parameters.

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