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

Annotations already declare readOnly/idempotent/openWorld, so the safety profile is covered; the description adds genuinely new context: the result is a range plus the biggest-saving task, the per-task shares derive from IPPR and McKinsey research, and no API key is needed. It stops short of noting that all-zero inputs produce a trivial result, but the added value over annotations is real.

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?

Two tight sentences: purpose and task enumeration first, then return shape, cost and docs link. The parenthetical task list is long but earns its place by mapping to the eight parameters. No filler sentences.

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?

With no output schema, the description must explain the return value, and it does: a range plus the highest-saving task. Combined with the fully documented schema and read-only annotations, an agent has everything needed to call this correctly without opening the docs link.

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 coverage is 100% and every parameter already documents its unit, range and default, so the schema carries the load. The description contributes the framing that inputs are hours per person per week across seven task types and that people scales it to a team, which is mildly additive but not new syntax or format detail.

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 and resource ("Estimates the hours a week AI could save") plus the exact input domain: seven named task types. An agent can tell this is a time-savings estimator rather than an audit or readiness score. It does not, however, distinguish itself from the sibling calculate_ai_savings, which sounds like a near-duplicate.

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?

"one person or a team" and the per-task default of 0 imply how to call it, and "Free, no key" removes an auth concern. But there is no explicit when-to-use / when-not guidance and no routing away from calculate_ai_savings or estimate_ai_staff_impact, so the agent must infer the boundary between these overlapping calculators.

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