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

Description discloses that it's a read-only consultation (supports readOnlyHint), does not involve sensitive data ('não é dado sigiloso'), and clarifies the LGPD responsibility of the client as data controller. It also mentions the payment model and that it's hosted by the platform. 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?

Description is concise but informative, covering purpose, usage, and context in a few sentences. It's not overly verbose. However, it could be more structured, but it's acceptable.

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 description gives context about the official source, payment, and LGPD, but lacks details on when to use vs siblings, and does not explain the parameters. Since there are 5 required params, more context would be helpful. It also doesn't mention output format or what information is returned.

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 schema has 5 required parameters but no descriptions. The description mentions credentials (a3, a3_pin, login_cpf, login_senha) and chassi (likely the vehicle chassis), but does not explicitly explain each parameter's purpose or format. With 0% schema description coverage, the description partially covers the parameters but not fully. It's ambiguous what a3 and a3_pin are exactly.

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 what the tool does: it consults judicial blocking restrictions from RENAJUD via an official source. It is distinct from sibling tools like 'authenticate' or 'marketplace', which are general platform functions. The name and description align, and it specifies the resource (RENAJUD restrictions) and the action (consult).

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 on when to use this tool: for querying RENAJUD judicial blocking information from official Brazilian sources encoded in ECRVSP. It mentions payment via prepaid credits and that no platform credentials are needed (though user credentials are required in the schema). It doesn't explicitly contrast with siblings, but the purpose is clear enough to differentiate.

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