ZenMoney Accounts

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

No annotations provided. Description hints at reading from an in-memory snapshot but does not disclose if data is stale, requires prior sync, or any side effects. Basic behavioral context is missing.

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?

Single sentence with no extraneous information. Efficiently conveys the core purpose.

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?

Tool has one optional parameter, no output schema, and moderate complexity. The description lacks details on return fields, pagination, or the effect of the parameter, leaving the agent with insufficient context for correct 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?

Schema description coverage is 0%. The description does not explain the 'includeArchived' parameter or its effect. For a 0% coverage, the description should provide meaning beyond the schema but fails to do so.

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 the verb 'list' and resource 'accounts' with a specific context 'in-memory ZenMoney snapshot', distinguishing it from sibling tools like zenmoney_list_budgets or zenmoney_list_tags.

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 like zenmoney_list_budgets or zenmoney_sync. The description implies a read operation but does not specify prerequisites or exclusions.

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