list_transactions

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

No annotations are provided, so the description carries the full burden. It discloses pagination, sort/filter support, tier restrictions, and API key requirement. However, it does not explicitly state that the operation is read-only or describe any side effects, which would enhance transparency.

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 four short sentences that front-load the core purpose and then provide essential context (pagination, sort/filter, tier limits, auth). Every sentence adds value with no redundancy or fluff.

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 has 5 parameters, no output schema, and no annotations, the description covers pagination, tier restrictions, and authentication but omits details like default page size, how pagination works, the return format, and specifics of filter parameters beyond 'sort/filter query params'. It meets a minimal threshold but 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 only 20% (only 'sort' has a description). The description says 'Supports sort/filter query params' but does not elaborate on any specific parameter beyond what the schema already provides. It fails to compensate for the low coverage with additional parameter explanations.

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 'List the authenticated user's transactions, paginated.' This is a specific verb+resource combination that distinguishes it from sibling tools like list_buy_list or list_inventory. It also mentions support for sort/filter params, reinforcing its purpose.

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 context about tier limitation (free vs premium) but does not explicitly state when to use this tool over alternatives or when not to use it. No sibling tools are mentioned for comparison, so guidance is limited to implicit conditions.

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