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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond those: pay-per-query with prepaid credit, no platform credentials needed, official/public source, non-confidential data, and LGPD controller responsibility.

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 compact and front-loaded with the core purpose. The additional sentences about payment and LGPD are useful context rather than filler, though the legal sentence is slightly dense and could be tightened.

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 tool with 14 parameters, no output schema, and no usage guidance, the description is not complete enough. It explains the data source and legal framing but does not describe return values, required input meaning, expected certificate format, result limits, or any invocation prerequisites.

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 description coverage is 0% and there are 14 parameters, but the description provides no guidance on any of their meanings, formats, relationships, or required combinations. Fields like tipo_certidao, endereco, rg, orgao_expedidor_rg, and birthdate are completely uninterpreted.

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 opens with 'Tribunal TJRS: Certidão do 1º Grau, consulta em fonte oficial', identifying a specific verb (consulta) and resource (first-grade certificate from the TJRS court). This clearly distinguishes it from sibling tools like authenticate, marketplace, and report_bug.

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 gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives. It implies usefor TJRS first-degree certificate lookup, but that is mainly inferred from the tool name rather than stated operationally.

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