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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the data source (CARF) and lookup key (CPF/CNPJ); it does not disclose response shape, pagination, or behavior when both identifiers are supplied.

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 one compact, front-loaded sentence with the acronym expanded in parentheses. Every word is useful and there is no extraneous detail.

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?

For a 3-parameter tool with no output schema, this description is incomplete. The optional 'completo' parameter, the expected output format, and how CPF/CNPJ are expected to be provided are all missing, leaving an agent to guess at correct invocation.

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 schema description coverage at 0%, the description must compensate, but it only mentions CPF/CNPJ as lookup keys. The 'completo' boolean parameter is entirely unexplained, and the relationship/alternation between CPF and CNPJ is ambiguous.

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 states the tool returns processes in CARF (an administrative tax appeals council) keyed by CPF/CNPJ. It is distinct from sibling compliance tools due to the specific CARF data source, though there is no explicit verb like 'list' or 'search'.

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 context is given for when to use this tool versus any of the many sibling compliance_* tools. The description does not say when CPF vs CNPJ should be used or mention any alternative for similar queries.

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