get_transactions

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

With no annotations, the disclosure 'Returns up to 100 transactions sorted most-recent first' provides important behavioral traits (limit and sorting). It does not mention rate limits, authentication requirements, or side effects, but for a read operation it is fairly transparent.

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?

Three short sentences that front-load the main purpose and efficiently convey all key information. No wasted 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?

Given the tool's complexity (3 optional params, output schema exists), the description covers purpose, filtering, limit, and sort order. It does not mention the default for 'days' or confirm that it returns only transactions from connected accounts (stated in purpose). Mostly 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?

The description adds meaning beyond the schema by explaining 'search' filters by keyword (merchant/description) and 'min_amount' sets a minimum dollar amount. The 'days' parameter is implied by 'recent' but not explicitly described, leaving a minor gap.

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 'Fetch recent transactions from all connected accounts,' specifying the verb (fetch), resource (transactions), and scope (all accounts). This differentiates it from siblings like 'list_accounts' or 'get_asset_allocation'.

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 when-to-use guidance through filtering options ('keyword (merchant/description)' and 'minimum dollar amount'). It does not explicitly state when not to use or name alternatives, but the purpose is distinct enough.

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