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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds the unit of the output (revenue per day), which is meaningful context, but says nothing about edge cases such as zero opportunities or zero cycle length.

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 well front-loaded and information-dense. The second sentence is a promotional URL that carries no operational value for an agent invoking the tool, so the definition is not entirely free of waste.

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 pure four-parameter calculator with no output schema and full annotation coverage, the description supplies what is needed: the computed quantity and its unit. It would be stronger with the underlying formula or handling of degenerate inputs, but nothing essential for a correct call is missing.

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 inputs (openOpportunities, winRatePct, avgDealValue, cycleDays) are already documented with type and meaning. The description restates the same inputs in prose without adding units, ranges, or format details beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (calculate) and resource (sales velocity) and defines the metric as revenue generated per day, with the four driving inputs named. This is enough to distinguish it from neighbors like sales_cycle_length_forecaster or sales_pipeline_leak_evaluator, though it never explicitly says how it differs from them.

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?

There is no guidance on when to reach for this tool versus the many adjacent pipeline/velocity calculators in the sibling list, and no prerequisites or exclusions are stated. The description only says what it computes, leaving the selection decision entirely to the agent.

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