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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that consultation is paid per use with prepaid credits, hosted by the platform, and the data is public from official Brazilian sources. It also discloses data subject responsibilities under LGPD. This goes beyond annotations and explains cost implications and data control, though it could have detailed response format or rate limits.

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, well-structured paragraph that covers purpose, hosting, authentication, cost, data source, legal compliance, and data handling. Every sentence adds value without being overly verbose.

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 simple read-only query with one parameter and minimal schema, the description covers usage context, cost model (prepaid credits), and legal compliance. It doesn't explain what to do if the CNPJ is invalid or the licensing information is not found, but given the simplicity of the tool, this may be sufficient.

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 coverage is 0% in the description, but with only one parameter (cnpj), the description notes the format in the purpose ('pelo CNPJ'), which adds some semantic value. However, the description doesn't specify CNPJ mask requirements, length, or format. Since there is only one parameter and the description does mention it, this is adequate but not extensive.

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 performs a public license consultation for a company at JUCESP by CNPJ. It is specific about the resource (JUCESP licensing), the verb (consult), and differentiates from siblings by mentioning the specific Brazilian registry context.

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?

The description implies usage context (public consultation via CNPJ) and notes it is hosted on the platform without credentials, but does not explicitly explain when to use this tool versus alternatives or mention sibling tools. Some guidance on legitimate use (LGPD) is given, but no direct comparison to alternatives.

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