Consultar saldo da conta Pix

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

Annotations already mark readOnlyHint true; description adds that blocked values are shown when requested and confirms no balance movement, aligning perfectly and adding value.

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?

Two concise sentences conveying all essential information without waste, well front-loaded.

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?

Given read-only nature, one optional param, and existence of output schema, the description covers purpose, usage, and safety completely.

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 coverage is 100% with one parameter. Description's 'quando solicitado' hints that 'bloqueios' triggers blocked value retrieval, adding meaning beyond schema's vague description.

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?

Description specifies verb 'consulta' and resource 'saldo da conta Efí', with optional blocked values, clearly distinguishing it as a balance query tool among many Pix siblings.

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?

Explicitly advises use 'antes de operações de saída ou em conciliações' and confirms 'nenhum saldo é movimentado', providing clear context. No explicit exclusion of alternatives but sufficient given tool type.

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