camelot_emergency_fund_planner

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

The description notes 'Local browser processing,' which adds meaningful behavioral context beyond the annotations. It also frames the tool as a non-destructive estimator, consistent with idempotentHint=true and destructiveHint=false. No contradiction with annotations exists.

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 short and front-loaded with the tool's primary purpose. It earns its place with the valuable local-processing note and canonical URL, though the stray double period after 'choose' is a minor polish issue.

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?

For a simple calculator with fully documented parameters, sensible defaults, no required fields, and an output schema present, the description is complete enough. It states the core calculation, the data referenced, and the privacy-relevant local-processing behavior.

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 input schema has 100% description coverage with defaults for all four parameters, so the structured fields already carry the semantic load. The description adds no parameter-level detail beyond referencing 'monthly expenses and runway you choose,' which maps to existing schema descriptions without new information.

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 states a specific action and resource: 'Estimate a cash reserve target from the monthly expenses and runway you choose.' This clearly identifies the tool as an emergency-fund calculation tool and distinguishes it from sibling financial planners by its explicit focus and calculation scope.

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 gives no explicit guidance on when to use this tool versus alternatives such as camelot_quick_budget, camelot_cash_flow_projection, or camelot_retirement_scenario_planner. The intended use is only implied by the tool's name and the 'estimate a cash reserve target' phrasing.

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