list_transactions

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

Covers pagination, filtering, tier restrictions, and API key, which is good given no annotations. However, does not mention rate limits, idempotency, or response format. Acceptable but not comprehensive.

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 concise sentences with front-loaded main action. Each sentence adds value: purpose, filter support, tier/auth info. Could be slightly more structured but overall efficient.

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?

With 5 optional parameters and no output schema, the description omits details on return format, error handling, and specific filter parameters. The generic 'sort/filter' reference is insufficient for proper invocation.

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?

Only 20% schema coverage (sort param described); description merely mentions 'sort/filter query params' without detailing individual parameters. The schema lacks descriptions for page, limit, order, type, and the description does not compensate.

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?

Clearly states the verb 'List', the resource 'transactions of the authenticated user', and specifies pagination and sort/filter support. Distinguishes from sibling tools like 'list_inventory' and 'list_notifications' by focusing on transactions.

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?

Provides context on tier-based data access ('Free tier sees last 30 days; Premium full history') and authentication requirement ('Requires IWMM_API_KEY'). Lacks explicit when-not-to-use guidance or alternative suggestions.

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