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

Beyond the read-only and non-destructive annotations, the description discloses that the tool requires prepaid credits and works without platform credentials. It also states that the data is not confidential and clarifies the client's data controller role, adding useful behavioral context.

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 relatively short but repeats similar points about official sources, payment, and privacy. Some legal language (LGPD) and repeated statements could be condensed without losing essential information.

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?

The description gives key context about the certificate's official nature, payment requirements, and data privacy. However, it does not describe the output format, required input combinations, or how to interpret results, leaving significant gaps for a user unfamiliar with the domain.

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 description provides no explanation for any of the 14 parameters. Parameter names like 'abrangencia', 'tipo_documento', and 'nome_social' are ambiguous without descriptions, and the schema also lacks explanatory text, leaving users to guess their meanings and usage.

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's action (querying a distribution certificate) and its target (TRF3). It explicitly mentions the official source and distinguishes the tool from other possible certificate queries by specifying the court and type.

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 provides no guidance on when to use this tool versus alternatives. It mentions payment and lack of platform credentials, but these are operational requirements rather than usage conditions or recommendations.

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