list_transactions

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully discloses that results are paginated at 50 per page and that time bounds are ISO-8601 UTC, but it does not mention whether the operation is read-only, requires permissions, or any rate limits. No contradictions with annotations.

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 two short sentences: the first states purpose and pagination; the second explains the parameters. It is front-loaded and contains no 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?

Given an output schema exists, return values are covered. The description explains pagination and the filtering mechanism, which is sufficient for a list tool. It does not mention ordering or defaults, but these are minor gaps for a simple listing endpoint.

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 0%, so the description must explain the parameters. It correctly names modified_after/modified_before (with format ISO-8601 UTC) and cursor for paging, giving them meaning beyond just field names. Cursor is not deeply defined, but adequate for usage.

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 action ('List'), the resource ('financial transactions for orders and donations'), and the page size. This distinguishes it from sibling list tools like list_orders (which lists orders, not transactions) and list_profiles.

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 implies usage by stating what it lists and how to filter/page, but it does not explicitly compare against alternatives or state when not to use it. There is no mention of prerequisites or exclusions, so guidance is only implied.

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