ZenMoney Transactions

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

Description only says 'list transactions' but lacks disclosure of behavioral traits such as read-only nature, side effects, authorization needs, or pagination. No annotations provided to compensate.

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?

Extremely short (one sentence) but lacks essential detail. Conciseness is not simply brevity; it should pack useful information without waste. Here, it's under-specified.

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 8 parameters, no output schema, no annotations, and multiple sibling tools, the description is severely incomplete. It does not explain query parameters, return structure, or behavior.

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 coverage is 0% and description adds no parameter information for any of the 8 parameters. Description fails to explain filtering capabilities like date range, account, or tags.

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?

Description clearly states 'List transactions' with a specific resource and source ('in-memory ZenMoney snapshot'). However, it does not differentiate from sibling tools like transactions_get or transactions_suggest.

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?

No guidance on when to use this tool versus alternatives. Does not mention when-not-to-use or prerequisites.

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