ZenMoney Merchants

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

The description mentions the data source (in-memory snapshot) which implies a read-only, possibly cached operation, but it does not disclose other behavioral traits such as whether syncing is required first, the speed of access, or any side effects. With no annotations, the description carries the full burden and falls short.

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 very short and to the point, which is good for conciseness. However, it lacks crucial information about parameters and usage, making it under-specified rather than appropriately concise. It earns a middle score for brevity but at the cost of completeness.

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 absence of output schema, annotations, and parameter documentation, the description is severely incomplete. It does not explain what the response looks like, how to filter merchants, or any constraints. A tool with two parameters and no additional context requires far more detail.

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?

The schema description coverage is 0%, meaning the schema itself provides no textual explanation for the parameters. The description does not elaborate on the 'query' or 'limit' parameters, leaving their semantics completely unclear. This fails to add value beyond the raw schema.

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 action (list) and the resource (merchants) with a specific source (in-memory ZenMoney snapshot). However, it does not differentiate itself from other list tools like zenmoney_list_accounts or zenmoney_list_tags, leaving ambiguity about when to use this particular tool.

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 is provided on when to use this tool versus its siblings or when not to use it. An explicit mention of context (e.g., 'use after syncing') or alternatives would significantly improve this dimension.

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