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 well covered. The description adds domain context about the CEIS registry's content (unfit/suspended companies), but does not disclose behavior like pagination, result format, or any special data source nuances. No contradiction with annotations exists.

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 a single concise phrase with no fluff or repetition. It front-loads the essential registry name and scope. However, it is so terse that it sacrifices useful detail, so it does not reach the top tier of conciseness that balances brevity with explanatory 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?

Given 3 parameters with no schema descriptions, no output schema, and no usage guidance, the description is too sparse to fully enable correct tool invocation. It does not address what 'completo' controls, whether both identifiers can be supplied, or what the response looks like. The tool's simplicity offsets some of this, but the coverage gap remains significant.

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% for the three parameters (CPF, CNPJ, completo). The description clarifies that CPF and CNPJ are lookup identifiers, but it does not explain the 'completo' parameter at all. It also omits format expectations (e.g., digits only, requiredness) despite missing schema descriptions, leaving a significant semantic gap.

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 (CEIS) and its content ('empresas inidôneas e suspensas'), plus the lookup key ('por CNPJ/CPF'). This distinguishes it from sibling compliance tools for other registries. However, it lacks an explicit verb like 'consult' or 'search', relying on the tool name and context to imply the query action.

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 provided on when to use this tool versus alternatives. It simply states the registry and lookup key, without mentioning exclusions, prerequisites, or which sibling tools cover overlapping or complementary registries. The agent must infer usage from the name and domain context.

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