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

Annotations already declare this a safe, idempotent, read-only, closed-world computation, so the safety profile is fully covered. The description adds that it is a 'how much would a cut buy you' simulation, but says nothing about output form (e.g., months of runway, delta) or how the increase is computed.

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 first sentence is front-loaded and efficient. The second sentence is purely a promotional link to an external site, which adds no selection or invocation value for an agent and does not earn its place.

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 low-complexity, fully-specified four-parameter calculator with no output schema, the description conveys the input concept and the general output idea but not the return shape or units. It is adequate but leaves the agent guessing what the result actually represents.

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 100%, so all four parameters (including burnReductionPct) are already documented in the schema. The description maps loosely to cash/burn/revenue but adds no units, ranges, or interpretation beyond what the schema provides, making the baseline 3 appropriate.

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 names a specific computation (how much extra cash runway a gross-burn cut buys) and the inputs it reacts to, so the agent knows the tool's function. It does not, however, distinguish itself from the closely-related burn_rate_optimization_forecaster or rule_of_40_sandbox 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?

It implies the scenario in which the tool applies (when you have current cash, burn, and revenue and want to model a burn cut), but offers no explicit when-to-use guidance, no exclusions, and no named alternatives among the many financial calculators.

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