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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description goes beyond these by explaining the commercial model (prepaid credit per query), the hosting arrangement, the non-confidential nature of the data, and LGPD responsibilities for the client as data controller. It also hints at authentication needs (login credentials or PKCS12 cert) without contradicting annotations. This enriches the behavioral profile significantly.

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 a single block of text that front-loads the core purpose ('Protestos, consulta em fonte oficial') then adds context on payment, data source, and legal responsibility. It is somewhat verbose (four clauses) but every sentence adds value, mixing technical, commercial, and compliance details. No wasted words, though it could be tightened by removing redundant emphasis on 'fonte oficial'.

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?

With 6 parameters, no required fields, no output schema, and no enumeration, the description needs to fill gaps about invocation. It provides high-level context (paid, official, LGPD) but omits critical operational details: how to choose between cpf and cnpj, how authentication works (login vs PKCS12, are they alternatives?), and what the response structure looks like. It is not minimal but leaves the agent guessing on usage mechanics, so it's incomplete for a tool of this complexity.

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 6 parameters with zero description coverage. The description mentions the tool queries official sources but does not explicitly map parameters like cpf/cnpj as query identifiers or login_cpf/login_senha and pkcs12_cert/pkcs12_pass as authentication methods. It leaves the agent to infer that cpf/cnpj are probably the search keys, but gives no guidance on which are required or how they interact. The description fails to compensate for the schema's lack of parameter documentation.

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 purpose: querying protest records (Protestos) from the official IEPTB/CENPROT source. It specifies the resource (protest records) and action (consultar), and distinguishes it from sibling tools which focus on authentication, marketplace, etc. The verb 'consultar' combined with the domain 'IEPTB (CENPROT)' leaves no ambiguity about the operation.

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: it mentions the tool is hosted on the platform, requires prepaid credits per query, does not use platform credentials, and queries official Brazilian sources with the same data available to citizens. It doesn't explicitly state when not to use the tool or name alternatives, but given the siblings are unrelated, this is adequate. It implies this is for legitimate citizen-accessible data queries.

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