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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description adds critical context: 'sem credenciais da plataforma' (no platform credentials), 'pague por consulta com crédito pré-pago' (pay per query with prepaid credit), and LGPD data controller responsibilities. This enriches the agent's understanding of cost, authentication, and legal 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 front-loaded with the purpose statement, followed by operational and legal context. It is not overly long, but some sentences (e.g., 'Hospedado pela plataforma') could be trimmed. Overall, it is organized and each sentence adds some value.

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?

With no output schema, the description should explain what data is returned, but it only vaguely says 'Dados Cadastrais'. It omits return structure, error conditions, and example usage. Given the tool's simplicity, it is still incomplete for an agent to fully anticipate outcomes.

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%, and the description does not mention the 'pis' parameter or its meaning. This is a single-parameter tool, and the description fails to explain what PIS is or how to provide it, leaving the agent without necessary semantic information.

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 a 'consulta' (query) for 'Dados Cadastrais' (registration data) from the Receita Federal SAL system. It distinguishes itself from sibling tools, which are meta/utility tools (authenticate, connect, etc.), not data lookup tools. However, it could be more explicit about the specific resource and what data is returned.

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?

No explicit guidance on when to use this tool versus alternatives. While siblings are not similar, the description does not state a clear use case (e.g., 'use this when you need PIS registration data'). It mentions platform hosting and payment but does not provide exclusions or prerequisites.

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