pendingTransactions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Retrieve' implies a read-only operation, but the description does not disclose pagination behavior, sort order, time windows, response shape, or any other runtime behavior an agent would need to anticipate.

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 one tight sentence with the core action front-loaded and a useful parenthetical qualifier. There is no redundant phrasing or filler.

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?

For a simple paginated list tool with two clearly documented parameters, the description is reasonably complete. However, there is no output schema and no annotations, and the description does not explain the default pagination behavior, the response format, or precisely what qualifies a transaction as 'pending.'

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 description coverage is 100%: both 'page' and 'limit' are already documented in the input schema. The description adds no additional meaning or guidance about these parameters, so the baseline score of 3 applies.

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 uses a specific verb ('Retrieve') and a specific resource ('a list of pending transactions'), making the tool's purpose immediately clear. The parenthetical clarifies the business value, and the 'pending' qualifier distinguishes it from sibling tools like failedTransactions and findTransactions.

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 parenthetical 'helps track delayed settlements/payouts' provides an implied usage context. However, the description never explicitly states when to use this tool over alternatives like findTransactions or failedTransactions, nor does it mention conditions where the tool should not be used.

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