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

Annotations already indicate read-only, idempotent, non-destructive behavior. Description adds valuable context: it's free, resolves CNPJ to legal name and partners, searches DJEN, and provides complete process numbers. No contradiction with annotations.

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?

Description is concise (one paragraph, three sentences) with no wasted words. Front-loaded with the key function ('DESCOBERTA por CNPJ'). Every sentence adds 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?

Comprehensive for a simple tool with two parameters and no output schema. Covers input, optional behavior, output elements (complete process numbers), and next steps (enrichment with datajud). Minor gap: no error handling or format specifications for CNPJ.

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 has 0% parameter descriptions. The description explains both parameters: 'cnpj' is implied in 'resolve o CNPJ' and 'incluir_socios' is clarified as optional inclusion of partner processes. Adds meaning beyond the raw schema.

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 states the tool resolves a CNPJ into a legal name and partners, searches for processes by name in DJEN, provides complete process numbers, and optionally includes partner processes. It distinguishes from siblings like 'cnpj_consultar' by specifying the process search aspect.

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?

Provides explicit context on when to use (resolving CNPJ and searching processes) and optional behavior (include socios). Offers post-usage guidance to enrich with datajud tools. Does not explicitly exclude alternative tools but implies appropriate use.

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