square_list_payments

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

Annotations are absent, so the description carries the full burden, but it discloses no behavioral traits beyond the basic listing function. Missing details on pagination, ordering, rate limits, authorization requirements, or what happens when no filters are provided.

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, with the purpose front-loaded and parameter details clearly listed. Every sentence adds value, but parameter explanations could be more structured (e.g., grouping optionality).

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?

Despite having an output schema, the description lacks context on common usage patterns, pagination behavior, date range constraints, and how to effectively use optional filters. The minimal information may leave an agent uncertain about expected behavior.

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 0%, but the description adds semantic meaning for all three parameters: explains 'from_date' as begin time (RFC 3339), 'to_date' as end time (RFC 3339), and 'location_id' as filter by location. This compensates well for the bare schema, though default behavior is not clarified.

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 'List Square payments for the connected merchant account,' specifying the verb (List), resource (Square payments), and scope (connected merchant account). This distinguishes it from sibling tools like square_get_payment (single payment) and square_list_payouts (different resource).

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 such as square_get_payment or list tools from other providers. No usage context, exclusions, or when-not-to-use information is given.

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