Get Pending Transactions

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

Although annotations already declare readOnlyHint=true, the description adds substantial behavioral context beyond that: pending entries affect available balance immediately, can change or vanish, are not returned by get_transactions until settlement, and lack an id. It also describes the response shape and key field semantics, which is valuable given the dynamic nature of pending transactions.

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 stays reasonably concise. It does enumerate return fields even though an output schema exists, which is somewhat redundant, but the added notes about pending behavior and missing id are useful rather than wasteful.

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?

Given the zero-parameter schema, readOnly annotation, and existing output schema, the description is complete enough for an agent to call the tool correctly. It covers the key behavioral caveats around pending transactions and return semantics without leaving material gaps.

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 tool takes no parameters, so there are no parameter semantics to explain; this matches the baseline of 4 for zero-parameter tools. The schema is empty with additionalProperties false, and the description does not need to add parameter detail.

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 and resource: list all pending, not-yet-settled transactions across the user's accounts. It also distinguishes this tool from get_transactions by explaining that pending entries do not appear there until settlement, and the 'across the user's accounts' phrasing implicitly contrasts with the account-scoped sibling. An agent can identify the tool's role without opening the schema.

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 gives clear usage context: pending transactions affect available balance immediately but are absent from get_transactions until they settle, and may change or disappear. However, it does not explicitly name acct_get_pending_transactions as the per-account alternative or state when not to use this tool.

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