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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds only that it concerns 'private entities impeded' but doesn't elaborate on return format, pagination, or authorization needs, providing minimal extra context.

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 extremely short, which is concise but under-specified. It lacks any structure or detail; while it has no fluff, it also doesn't earn full marks for conciseness because it omits essential information.

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 tool with 0% parameter coverage and no output schema, the one-line description is insufficient. It doesn't explain expected inputs, output semantics, or how 'completo' changes behavior, making it hard for an agent to use correctly.

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 explain the 'CNPJ' or 'completo' parameters at all. With no compensation, the agent has no idea what values to provide or what 'completo' controls.

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 identifies the specific registry (CEPIM) and key (CNPJ), implying a lookup/check operation. It's clear but lacks an explicit verb like 'check' or 'query', and it doesn't differentiate from the many sibling compliance tools other than by name and registry type.

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 guidance is given on when to use this tool vs. the extensive list of sibling compliance tools. It doesn't mention any exclusions, dependencies, or typical use cases.

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