Get Transactions

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

The readOnlyHint annotation already declares the operation as safe. The description adds the default 90-day window, which is also present in the schema defaults, so little additional behavioral context is provided. No pagination or result format is mentioned, but with annotations the bar is lower.

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?

A single, information-dense sentence. It front-loads the purpose and immediately states the default behavior, with no filler words.

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 read-only transaction retrieval tool with fully documented parameters and a readOnlyHint, the description covers the core purpose and default behavior. It doesn't specify the response shape, but the absence of an output schema lowers the expectation, and the tool's purpose is unambiguous.

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%, so all three parameters are fully documented. The description does not add additional meaning beyond the schema; it only mentions the account and default range, which the schema already covers.

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 the specific verb 'Get' with resource 'transactions for a bank account', clearly distinguishing it from sibling tools like list_accounts or get_connection_accounts. The default date range adds precision.

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 provides clear context (retrieves transactions for a bank account, defaults to last 90 days) but does not explicitly name alternatives or when-not-to-use scenarios. Since no sibling tool handles transactions, the context is sufficient.

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