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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: no credentials required, pay-per-query with prepaid credit, data source is public/official, and the client is the LGPD data controller. 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?

The description is three sentences with the purpose upfront, followed by payment/hosting and legal context. It is economical and not padded, though the legal sentence adds some length without affecting core usage.

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?

This is a complex 11-parameter tool with no output schema. The description explains the high-level purpose, data sensitivity, and legal role, but omits parameter formats, expected return values, and behavior for missing/invalid data. The agent would still have significant uncertainty when invoking 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?

Schema description coverage is 0%, so the description must compensate. It mentions DNI, name, birth, and address, but 11 parameters exist and critical details are omitted: DNI format, date format, the role of Phone, Country, and the optional 'completo' flag. This is insufficient for an agent to correctly fill all required fields.

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 opens with a specific verb ('Verifica') and a clear resource ('a identidade de uma pessoa na Argentina'), and explains the method ('confrontando os dados informados'). This sharply distinguishes it from sibling tools such as authenticate, marketplace, and 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?

The description states when to use the tool (Argentine identity verification) and provides relevant context (platform-hosted, no credentials, prepaid credit, public data). It does not explicitly exclude scenarios or name alternatives, but the context is clear enough for an agent to select it appropriately.

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