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

The description discloses the payment model, the non-confidential nature of data, and LGPD responsibilities. It goes beyond the readOnly annotation by explaining the operational and legal context, though it does not mention potential errors or failure modes.

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 moderately concise but includes redundant legal phrasing. It could be trimmed, but the key points (query, payment, data sensitivity) are present without excessive verbosity.

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?

Given no output schema, the description need not explain return values. It covers the data source, payment, and legal responsibilities, which is sufficient for a simple query tool. Missing details like expected result format are acceptable.

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 only parameter 'cpf' has no schema description, and the tool description does not explain its format or purpose. With 0% schema coverage, the description fails to compensate by adding any meaning about the expected CPF value.

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 tool queries official Brazilian professional certificate records ('consulta em fonte oficial'). It distinguishes itself from generic sibling tools (authenticate, connect, etc.) by specifying its core function of querying certificate information.

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?

Provides usage context: pay-per-query with prepaid credits, no platform credentials needed, and notes the data is not confidential. It does not explicitly compare to alternatives, but the purpose is distinct enough that when to use is implicitly clear.

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