payway_get_transaction_details

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

With no annotations, the description carries the burden, and it does disclose a concrete constraint: the 10-requests/minute PayWay rate limit. It does not state what the returned details/history contain, whether any auth/permissions are required, or how errors/timeouts behave, but for a simple read lookup this is a moderate gap.

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 short sentences, front-loaded with the primary purpose and followed by the rate limit. No filler; every sentence contributes.

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 is simple (one required string parameter, no output schema), and the description covers purpose and a key operational limit. It omits response contents and parameter semantics, so an agent is left to infer the exact meaning of 'full details/history' and the tran_id format.

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?

The schema has no property descriptions (0% coverage), and the description never explicitly defines tran_id or its format. The parameter name and the phrase 'any past transaction' imply it is a transaction identifier, but the description adds no semantic detail beyond the schema.

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 states a specific verb ('Get') and a concrete resource: full details/history of any past transaction, with the temporal scope 'any age'. It is clear enough to distinguish it from list-oriented siblings like payway_get_transaction_list, though it does not name sibling alternatives explicitly.

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 phrase 'any past transaction (any age)' gives implied guidance that this tool is for historical single-transaction lookups. However, it does not state when to prefer this over payway_check_transaction or payway_get_transactions_by_merchant_ref, and gives no exclusions or alternative conditions.

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