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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safe-read profile is fully covered. The description adds a partial picture of what is returned (annual hours lost, revenue lost, freed capacity), which is useful since there is no output schema, but it says nothing about units, currency, or assumptions.

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 states the value proposition without waste. The second sentence is a promotional link rather than invocation-relevant information, which costs a point but is harmless.

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 three-parameter, closed-world read-only calculator with no output schema, the description names the salient outputs, which is enough to call it correctly. It would be stronger with a note on assumptions or how it differs from crm_roi_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 100%, so reps, hoursWastedPerWeek, and hourlyCost are already documented in the schema. The description adds no unit or format guidance (e.g. annualized vs weekly, currency) beyond that, so baseline 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?

The description states a specific verb-and-resource: it quantifies rep hours and revenue lost to bad CRM data plus capacity a cleanup frees. An agent knows what the tool computes, but it is not differentiated from the very similar sibling crm_roi_calculator, which risks mis-selection in this crowded family.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as crm_roi_calculator or data_enrichment_value_predictor. The agent must infer the scenario entirely from the name.

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