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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds meaningful behavioral context: no credentials are required, there is a prepaid credit cost model, the data is not confidential, and the caller is the LGPD data controller. This materially helps the agent understand side effects and obligations.

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 key purpose in the first sentence, and each subsequent sentence adds meaningful operational or legal context. No redundant filler is present, and the length is appropriate for the amount of information conveyed.

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 12 unrequired, undocumented string parameters and no output schema, the description is not complete enough for correct invocation. It explains the source and legal context, but does not specify which identifiers or filters are necessary, how to combine them, or what kind of certificate query inputs are accepted. The agent would need external knowledge to use this 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?

Schema description coverage is 0% across 12 parameters, and the description does not mention any parameter semantics, required combinations, or identifier selection guidance (e.g., when to use CPF versus CNPJ versus nome). The description adds no value beyond the raw property names in the schema, so the agent gets almost no help with parameter 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 a specific verb+resource: consulta/certidão do 1º Grau no Tribunal TJBA em fonte oficial. This distinguishes the tool from the generic sibling tools (authenticate, marketplace, etc.) and makes the main purpose immediately obvious.

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 usage context: hosted by the platform, no platform credentials needed, requires prepaid credit per query, and queries official Brazilian citizen-available data. It does not explicitly list exclusions or alternatives, but the context is strong enough for an agent to understand when this tool is appropriate.

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