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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds useful behavioral context: it's a paid query, hosted by the platform, returns non-confidential data, and includes LGPD compliance notes. This goes beyond the structured hints, though it doesn't detail side effects or return behavior.

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 a single informative paragraph covering purpose, hosting, payment, data source, and legal note. It's front-loaded with the main action and includes essential context without excessive verbosity, though some legal clauses could be considered extraneous.

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 does not explain the six input parameters (all optional), nor does it describe the output format or error conditions. Given 0% schema coverage and no output schema, the description fails to compensate for missing parameter documentation, leaving the agent without enough context to properly invoke the tool.

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 description provides zero explanation of the 6 parameters (email, senha, tipo_login, pkcs12_cert, pkcs12_pass, numero_pedido). Schema coverage is 0%, and the description doesn't mention any of them, leaving the agent with no semantic guidance for parameter usage.

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 identifies the action ('Download de Recibo') and resource ('Registradores (ARISP) Matrícula'), distinguishing it from sibling tools like 'authenticate' or 'connect'. It's specific enough to know it's a receipt download/query for registration, though it could be more explicit about the query nature vs download.

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 some context (hosted by platform, paid per query, no platform credentials) but does not explicitly state when to use this tool vs. alternatives like 'authenticate' or 'connect'. It mentions it's a paid consult but lacks clear exclusion or alternative guidance.

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