cashapp_get_transactions

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

No annotations are provided, so the description must carry the full burden. It only states the tool returns transactions and mentions a limit parameter, but fails to disclose behavioral traits such as ordering, freshness, pagination behavior, or any side effects. For a read operation, more context on data recency or scope would be valuable.

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 concise, consisting of two sentences that front-load the purpose. No wasted words, but it could be slightly more structured (e.g., separating purpose and output).

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 list tool with one optional parameter, the description covers the basic purpose and parameter. However, it lacks details on return format, ordering, or any practical constraints (e.g., maximum limit). Given no output schema, the description could be more complete.

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%, with the 'limit' parameter described as 'Maximum number of transactions to return. Defaults to 10.' The tool description adds no additional semantics beyond what the schema provides, so baseline 3 is appropriate.

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 the tool retrieves 'transaction history for the logged-in Cash App account' and returns 'a list of recent transactions'. The verb 'Get' and resource are specific. However, it does not explicitly differentiate from sibling tool 'cashapp_get_transaction_details', which likely focuses on a single 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?

No guidance is provided on when to use this tool versus alternatives like 'cashapp_get_transaction_details' or 'cashapp_get_balance'. The description lacks any 'when to use' or 'when not to use' context, leaving the agent without decision support.

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