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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds meaningful context: prepaid per-query cost, no platform authentication, official non-confidential source, and LGPD controller responsibilities. No contradiction with annotations is present.

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 compact and front-loaded with the tool's purpose, followed by cost, source, and legal context. It is slightly dense but contains no filler or repetition.

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?

For a tool with 5 parameters, no output schema, and no parameter descriptions, the description provides important safety and legal context but is insufficient for correct invocation. It leaves unclear which credentials are needed, how parameters combine, and what the response contains.

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?

All 5 parameters are undocumented in the schema (0% coverage), and the description does not explain renavam, login_cpf, login_senha, pkcs12_cert, or pkcs12_pass. The phrase 'sem credenciais da plataforma' even creates ambiguity about the credential-related parameters, so the description fails to compensate for the schema gap.

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 resource ('DER SP: Multas e Recursos') and the action ('consulta em fonte oficial'), making the tool's purpose identifiable. It is specific enough to distinguish from the listed platform-level sibling tools, though it does not state precisely what the query returns.

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 useful context: no platform credentials are needed, it uses prepaid credits, and it queries citizen-available official data. However, it never explicitly states when to use this tool versus alternatives or gives exclusion criteria.

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