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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true. The description adds useful behavioral context beyond that: the result is a pound range plus two or three insights, it is partial by design, and no key is required. It does not discuss assumptions or accuracy limits, so it is strong but not exhaustive.

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 description is front-loaded with the core estimate and then layers inputs, limitation, access note, and docs link. It is dense but every clause carries useful information, with only minor room to tighten.

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 pound range with two or three insights. It also explains the deliberate partiality and points to the full audit. It is nearly complete, though it could be clearer about calculation assumptions.

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 the schema already documents all four parameters. The description still adds meaningful semantics by naming the default sources: ONS 2025 UK median for hourly pay and Department for Education ranking for sector exposure.

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 estimates annual savings in pounds for a UK business from admin automation. It also scopes the calculation inputs. However, it does not explicitly distinguish this tool from siblings such as calculate_ai_time_saved or estimate_ai_staff_impact, so it falls short of a 5.

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?

The description implies usage by calling the result partial and pointing to the free AI audit for a full breakdown. But it does not clearly state when to choose this tool over sibling calculators, nor does it provide explicit when-not conditions.

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