getTransfers

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'List transfers', implying a read operation, but fails to mention authentication needs, response format, pagination, or any side effects. This is a significant gap for a tool with no structured metadata.

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 short phrase, 'Listar transferências', which is concise and front-loaded. However, it is arguably under-specified, providing just the minimal verb+resource without any additional structure or elaboration that would help the agent understand usage nuances.

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 no parameters and an existing output schema, the description is minimally sufficient. However, it lacks any context about what constitutes a transfer, how it differs from a transaction, or what the response contains. The presence of an output schema reduces the need to explain return values, but the description still leaves gaps in usage context.

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 input schema is empty (zero parameters), so the baseline is 4. The description adds no parameter information, but there are no parameters to document, and the schema fully covers the parameter surface.

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 uses a clear verb 'Listar' (to list) and specifies the resource 'transferências' (transfers), clearly indicating a collection-oriented operation. It distinguishes from the sibling 'getTransfer' (singular) by implying a list of all transfers, though it does not explicitly differentiate from 'getTransactions'.

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 no guidance on when to use this tool versus alternatives like 'getTransfer' or 'getTransactions'. There is no mention of context, prerequisites, or exclusions, leaving the agent without decision criteria for tool selection.

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