Listar locations de recorrência Pix Automático

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint. The description adds 'sem modificar suas associações' reinforcing read-only nature. No contradiction, but no extra behavioral details beyond that.

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 very concise: two sentences front-load purpose and usage. Every word adds value with no repetition or fluff.

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 the tool's complexity (nested params, output schema exists), the description is adequate but doesn't explain return format, pagination behavior, or what a 'location' is. Output schema may compensate, but textual cues are lacking.

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% but parameter descriptions are generic placeholders (e.g., 'Valor do campo “inicio” usado na entrada da operação'). The tool description adds no additional meaning or format guidance for parameters.

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 it lists locations for automatic Pix recurrences, specifying the resource and verb. It uses 'Lista locations destinadas a recorrências de Pix Automático' and distinguishes from siblings like pix_list_recurrence_automatic by focusing on locations.

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 says 'Use para localizar e acompanhar payloads recorrentes sem modificar suas associações', indicating when to use (read-only observation). However, it does not explicitly mention when not to use or name alternatives like detail or unlink tools.

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