Listar cobranças Pix com vencimento

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

Annotations already declare readOnlyHint=true, so the description's explicit statement 'sem modificar as cobranças encontradas' reinforces safety. No contradictions. Could add more about idempotency or side effects, but annotations cover key traits.

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 sentences: first defines purpose, second adds usage guidance. No redundant words. Every sentence serves a distinct purpose.

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 output schema exists and annotations are robust, the description covers purpose and safe usage. It could mention pagination or differentiate from similar list tools, but it already specifies 'with due date,' which is sufficient for basic selection.

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 description coverage is 100%, so the schema already documents each parameter. The description adds no parameter-level detail beyond 'com os filtros informados.' Baseline 3 is appropriate; it does not detract but adds minimal value.

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 clearly states 'Lista cobranças Pix com vencimento no período e com os filtros informados.' It specifies the verb (list), resource (Pix charges with due dates), and scope (period and filters). Distinguishes from siblings like pix_list_charges by focusing on due charges.

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?

Description says 'Use em rotinas de acompanhamento e conciliação sem modificar as cobranças encontradas.' It provides context (monitoring/reconciliation) and explicitly states it does not modify charges. However, it does not compare to alternatives or state when not to use.

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