paymentSessions.listTransactions

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

No annotations provided, so description carries full burden. While 'List' implies read-only, it does not confirm non-destructive behavior, disclose pagination limits, explain transaction types returned, or describe the response structure.

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?

Extremely brief (6 words) and front-loaded, but inappropriate brevity given zero schema coverage and lack of annotations. Every sentence must earn its place; this one barely introduces the subject.

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?

Inadequate for a financial transaction tool with zero annotations and no output schema. Missing critical context: parameter semantics, return value structure, pagination behavior, and sibling differentiation.

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 0% and the description fails to compensate by explaining the 'id' parameter (presumably the payment session ID). No syntax hints or format examples provided.

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?

States the action ('List') and resource ('transactions for a payment session') but fails to distinguish from sibling tool 'paymentSessions.getTransaction' (singular vs plural/list scope) or clarify relationship to 'paymentSessions.list'.

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?

Provides no guidance on when to use this versus retrieving a specific transaction via 'getTransaction' or when pagination might be needed. No prerequisites or alternatives mentioned.

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