ghl_payment_transaction_list

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, confirming safe read behavior. The description adds value beyond annotations by explaining pagination (limit, offset), filtering capabilities, and OAuth scopes, which inform the agent of important behavioral aspects.

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 front-loaded with the core purpose and contains four sentences. It includes technical details like endpoint and OAuth scopes which, while not strictly necessary, add context without excessive verbosity. Slightly less concise than ideal but well-structured.

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?

The tool has many parameters and no output schema. The description covers filtering and pagination adequately but omits details on response structure, sorting, or total count. Given the complexity and absence of output schema, more completeness would be beneficial.

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?

Input schema has 100% description coverage, providing baseline value. The description adds semantic grouping of filter options (name, alt type, date range, etc.) and explicitly mentions pagination parameters, helping the agent understand which filters are available and how to page results.

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 retrieves a paginated list of transactions with filtering options. The verb 'List' matches the resource 'Transactions', distinguishing it from sibling tools like `ghl_payment_transaction_get` (single transaction) and `ghl_payment_subscription_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?

The description explains what the tool does but provides no explicit guidance on when to use it versus other list tools (e.g., `ghl_payment_order_list`). Usage context is implied through the resource name, but no exclusion or alternative recommendations are given.

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