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

The description adds meaningful behavioral context beyond the annotations: it discloses that the operation is a non-confidential official query, that it is paid via prepaid credits, and that LGPD data-controller responsibilities apply. No contradiction with the readOnly/idempotent/destructive annotations was found.

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 concise, front-loaded with the core purpose, and each sentence adds context (official source, payment model, legal responsibility). It could omit the LGPD clause without losing operational clarity, but it is not unnecessarily long.

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 tool has no output schema and no parameter descriptions, yet the description does not explain what inputs are needed or what a successful consultation returns. It covers the commercial and legal context well, but leaves a significant gap in operational detail for the agent to invoke 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 has 0% description coverage and the description mentions none of the three parameters (cpf, cnpj, numero_pedido). The description does not compensate by explaining what values should be provided, how they relate, or which combination is expected beyond the required numero_pedido.

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 action ('Visualizar Certidão, consulta em fonte oficial') and the specific target resource ('Tribunal TJSC'). It also distinguishes itself from the unrelated generic sibling tools by naming the court and the certificate-consultation purpose.

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 clear context: this is a paid, official-source consultation requiring prepaid credits and no platform credentials. It does not explicitly name alternatives or state when not to use it, but for a standalone certificate lookup tool, the guidance is sufficiently clear.

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