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

The description goes well beyond the annotations (destructive/idempotent hints) by disclosing return-code semantics (201 on creation, 200 when the CNPJ already exists), the ownership precondition, the 100-company cap, and explicit exclusions ('no partners or contacts; no analysis starts'). This is exactly the behavioral context an agent needs for a mutation tool.

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 content is valuable but delivered as one long, run-on paragraph with awkward phrasing ('the organization of the organization key', 'returns the one that the person removed from the list'). The core action is not front-loaded and the conditional branches are hard to parse.

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 carries the burden of explaining returns and does so via status codes and outcome descriptions. Side effects, quotas, and preconditions are all covered; only a clearer statement of alternatives is missing.

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 a single parameter and 100% schema description coverage, the schema already fully documents the CNPJ format and check-digit requirement. The description adds no parameter-level detail beyond what the schema provides, so the baseline score applies.

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 names a specific action and resource: importing a CNPJ into a new or existing organization. It is distinguishable from siblings like remove_company and search_companies, though the purpose is buried in verbose conditional phrasing rather than stated up front.

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?

It describes the two invocation contexts (with vs without X-Organization-Id) and the precondition that the caller must manage the target organization, which implies when it applies. However, it never explicitly contrasts with alternatives such as search_companies or select_company, so usage guidance remains implied rather than stated.

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