paymentSessions.getTransaction

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

No annotations provided, so description carries full burden. 'Get' implies read-only but description omits error handling (404 behavior), rate limits, auth requirements, or whether this operation is idempotent. Insufficient for a data retrieval tool.

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?

Single sentence is efficient and front-loaded with no wasted words. However, brevity is inappropriate for the complexity—two undocumented parameters require explanatory expansion.

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 tool with 2 required parameters and zero schema documentation. Fails to explain parameter relationships, output structure, or distinguish from similar sibling operations. 'Get by id' is insufficient context.

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 has 0% description coverage with two required ID fields ('id' and 'transactionId'). Description mentions 'by id' (singular) but fails to clarify which parameter is the payment session ID versus the transaction ID, leaving critical ambiguity unresolved.

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 verb ('Get') and resource ('payment session transaction') but adds minimal detail beyond the tool name. Does not distinguish from sibling 'paymentSessions.listTransactions' (list vs single get) or clarify relationship to 'paymentSessions.get' (session vs transaction).

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 'paymentSessions.listTransactions' or prerequisites like requiring a valid session ID. No 'when-not' or alternative guidance present.

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