ZenMoney Budget Status

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

The description explicitly states the operation is 'read-only', which is a key behavioral trait. However, no other behavioral details (e.g., authentication, response format, error conditions) are provided, and there are no annotations to supplement.

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 with no unnecessary words. However, it sacrifices necessary detail for brevity, making it slightly 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 the tool has 4 parameters, no output schema, and no annotations, the description is insufficient. It covers the basic purpose but lacks return value documentation, parameter descriptions, and error handling context.

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?

With 0% schema coverage, the description adds no value beyond the parameter names and types in the schema. It does not explain the meaning or expected format of month, tagId, includeChildren, or userId.

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 that the tool calculates read-only spending and remaining amount for a category budget. The verb 'calculate' and resource 'budget status' are specific and distinguish from sibling tools like budgets_list or transactions_get.

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?

The description does not provide any guidance on when to use this tool versus alternatives such as budgets_list or transactions_list. No context on prerequisites or exclusions is given.

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