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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses that each query costs money ('pague por consulta com crédito pré-pago'), that no platform credentials are needed, and includes LGPD data responsibility details. This adds significant behavioral context beyond annotations, though it could elaborate on the request lifecycle or error handling.

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 and front-loaded, starting with the core purpose and then covering payment, data source, and legal caveats. It is not bloated, though the legal disclaimer could be considered a separate note. Overall, every sentence earns its place.

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 covers cost, credential handling, and data sensitivity, which are useful for a complex tool with 6 parameters and no output schema. However, it does not mention the return format, how parameters relate (e.g., email/senha vs pkcs12_cert), or any specific usage examples, leaving the agent to guess on invocation details.

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?

With 0% schema description coverage and no explanation of the six parameters (email, senha, tipo_login, pkcs12_cert, pkcs12_pass, numero_pedido), the description fails to guide the agent on how to populate them. The phrase 'sem credenciais da plataforma' hints that credentials are for an external system, but this is minimal and does not compensate for the lack of explicit parameter documentation.

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 it is for downloading/querying 'Matrícula' from official sources, specifically mentioning ARISP, which is a specific verb+resource. It differentiates from the generic sibling tools like 'authenticate' and 'connect', though the relationship between 'download' and 'consulta' could be crisper.

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?

It provides context that this is a paid service using prepaid credit and does not require platform credentials, which helps set expectations. However, it lacks explicit when-to-use versus alternatives or exclusions, and does not reference sibling tools like 'authenticate' or 'connect' that might be confused with it.

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