ZenMoney Transactions

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

With no annotations, the description must disclose behavioral traits. It only mentions that data comes from an 'in-memory snapshot', hinting at caching but not explaining whether it reflects latest data, if mutations affect it, or any side effects. No information on read-only nature, rate limits, or destruction.

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 a single sentence of 9 words, earning its place by stating the core purpose. However, it could be expanded with key details without losing conciseness.

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 optional parameters, no schema descriptions, and no output schema, the description is severely incomplete. It fails to explain filtering criteria, pagination, defaults, or return value structure, leaving the agent underinformed.

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 compensate for parameter meanings. However, the description provides no information about any of the 8 parameters (dateFrom, dateTo, accountId, etc.), leaving the agent to infer from names alone, which is insufficient.

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 verb 'list' and resource 'transactions', and specifies the source as 'in-memory ZenMoney snapshot', which distinguishes it from sibling tools like 'zenmoney_list_accounts' and 'zenmoney_list_tags'. It is specific and unambiguous.

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 such as 'zenmoney_get_transaction' or 'zenmoney_sync'. No conditions, prerequisites, or exclusion criteria are provided.

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