calculate_churn_rate

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

Describes inputs and outputs (churn %, retention %, annualized rate) but does not explicitly state that the tool performs a read-only computation without side effects. With no annotations, the description carries the burden but leaves ambiguity about mutability.

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?

Three sentences, each contributing essential information: what it does, when to use, expected inputs, and outputs. Efficiently front-loaded.

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 calculation tool with complete schema descriptions and explicit mention of outputs, no additional context is needed. The description is fully sufficient.

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 has 100% description coverage for all three parameters, and the description only restates the inputs without adding new semantic meaning beyond what the schema provides.

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 the tool computes customer or revenue churn rate, specifies it's for SaaS retention analysis, and distinguishes itself from siblings by directing to list_bundles for related calculators.

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?

Provides clear context for when to use (SaaS retention analysis) and mentions list_bundles for related tools, but lacks explicit when-not-to-use instructions or direct alternatives.

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