calculate_emergency_fund

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

No annotations are provided, so the description must disclose behavioral traits. It mentions the tool returns a fund and savings timeline but does not state whether it is read-only, required permissions, rate limits, or side effects. This is insufficient for full transparency.

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 three efficient sentences, front-loading purpose and use, then inputs/outputs. Every sentence is necessary and concise.

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?

The tool is simple with three required parameters and has an output schema (not shown but present). The description covers purpose, inputs, and outputs (recommended fund and timeline). It is mostly complete, though it could explicitly reference the output schema.

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 100% with descriptions. The description lists inputs but adds no new meaning beyond the schema (e.g., 'income stability' maps to 'job_stability'). Baseline 3 as schema does the heavy lifting.

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 tool computes an emergency fund target (3-6 months of expenses) for personal financial planning. The verb 'compute' and resource 'emergency fund target' are specific and distinguish it from the many other 'calculate_' siblings.

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 specifies its use for personal financial planning and references 'list_bundles' for related finance calculators, providing context. However, it does not explicitly state when not to use this tool or compare it to alternative tools.

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