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

Beyond the readOnly/idempotent annotations, it discloses significant behavioral detail: the data is the same cut as the public /operadores page, groups are merged into one, fleet results are capped at 100 with fleetTruncated, CPFs are never exposed, and specific vulnerability thresholds are described. This far exceeds what annotations alone convey.

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 dense but not padded; every clause contributes substantive detail. The single long, comma/semicolon-heavy sentence is harder to scan than structured bullets, but it is appropriately sized for the tool's broad output profile.

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 the tool's one-parameter input and existing output schema, the description covers the important operational behaviors: query matching, group aggregation, found:false, truncation, privacy limits, and the included vulnerability/regulatory data. An agent has enough context to invoke and interpret the tool 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?

The schema already documents the single query parameter at 100% coverage. The description adds a concrete URL-slug example, explains the 8-digit CNPJ root usage, and clarifies that names/spellings may differ, which is valuable beyond the schema. This justifies a score above the high-coverage baseline.

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 identifies the resource as a company-side profile for Brazilian operator/owner groups and enumerates its contents. It does not explicitly contrast itself with siblings like jt_owner_group or jt_operators_stats, so it stops just short of fully differentiating from alternatives.

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 gives thorough input guidance: accepted query forms, URL slug pattern, CNPJ root handling, grouping of multiple CNPJs into one group, and found:false semantics. However, it never states when to choose this tool over related siblings, so tool-selection guidance is only implied.

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