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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description adds meaningful context beyond that: no platform credentials, prepaid per-query pricing, official Brazilian sources, non-confidential data, and LGPD controller responsibilities. There is no contradiction with the 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 front-loaded with the core purpose and each sentence contributes useful information about source, pricing, credentials, and legal context. It is slightly dense but not wasteful, and it avoids repeating the tool name or schema fields.

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 paid query tool with no output schema, the description covers official source, payment model, and data governance, but it omits the CPF input format and the shape/contents of the expected return value. The agent could select the tool confidently but would still lack some details needed to invoke it 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 only one parameter, cpf, with no description and schema coverage of 0%. The tool description never mentions CPF format, validation, masking, or how the value should be provided (e.g., 11 digits, with or without punctuation). A simple parameter, but the description still needs to compensate for the missing schema coverage and does not.

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 tool as a query for the BPC benefit from the official Brazilian Transparency Portal ('consulta em fonte oficial'). It is specific about the resource, and the sibling tools (authenticate, connect, marketplace, report_bug, etc.) are clearly unrelated, so it is well differentiated.

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 practical usage context: the tool does not require platform credentials, charges prepaid credit per query, and should be used for official public BPC data under a legitimate LGPD purpose. It does not explicitly state when not to use it or name alternatives, but the sibling set makes those alternatives obvious.

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