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

With no annotations, the description must carry the burden of explaining behavior. It does state the calculation intent and input/output, but it does not disclose underlying assumptions such as compounding frequency, whether contributions are at the start/end of the period, or any limitations. This is a baseline disclosure but lacks sufficient detail for a financial calculation tool.

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 two sentences, front-loaded with the primary purpose and then a concise list of inputs and output. Every sentence adds value, and there is no redundancy or filler.

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's simplicity (4 scalar parameters, no output schema), the description covers the essential aspects: what the tool does, what inputs are needed, and what output to expect. However, it lacks mention of calculation assumptions or edge-case behavior, which would be beneficial but not strictly required for a basic calculator.

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%, so the description must compensate. It does map natural language terms to parameters: 'target' (goalAmount), 'current balance' (currentSavings), 'annual rate' (annualRatePct), and 'years' (years). This gives meaningful semantics beyond the schema, though it does not explicitly note units (e.g., rate as percentage) or constraints, which are partially present in the 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 tool's function: 'Calculate the monthly savings you need to reach any goal.' It specifies the main output ('required monthly contribution') and mentions all input categories, distinguishing it from sibling calculators like required_savings_calculator or savings_drawdown_calculator by focusing on the monthly contribution needed.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for setting a goal and determining monthly savings, but it does not state exclusions, such as when to use a 'required_savings_calculator' or 'fire_calculator'. It also lacks any prerequisites or best-use context.

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