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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds unique behavioral context: payment per query via prepaid credit, data is public/official, and the client is the LGPD data controller. This enriches transparency without contradicting 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?

The description is three sentences, each adding distinct value: purpose, payment/hosting model, and legal/data scope. No filler or redundancy; front-loaded with the core action.

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 complex tool with 18 parameters and no output schema, the description is severely under-specified. It omits parameter explanations, expected response format, and any procedural details beyond 'no platform credentials'. The legal disclaimer and data source info are helpful but insufficient.

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 18 parameters and 0% schema description coverage, the description adds no meaning to any parameter. Required fields like instancia, tipo, nome, uf, municipio, and email are completely unexplained, leaving the agent to guess their semantics.

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 queries official TJSC certificate data ('consulta em fonte oficial'). It distinguishes from sibling tools which are platform-level (authenticate, connect, marketplace), but the phrase 'Pedido de Certidão' is slightly ambiguous as it could imply ordering rather than consulting.

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 context (prepaid credit, no platform credentials, official Brazilian sources) but does not explicitly state when to use this tool versus alternatives. Sibling tools are generic platform utilities, so the distinction is implicit but not articulated.

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