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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds what the result contains, but says nothing about the reporting-year coverage, the 250+ employee statutory threshold, or behaviour for non-reporting employers.

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 sentences, no filler, with the load-bearing statement of what is returned front-loaded after the scope clause. Every clause earns its place.

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 usefully enumerates the returned metrics, which is the main missing piece an agent would need. It stops short of covering reporting-year scope, coverage limits and failure modes for employers without a published report.

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?

Only one parameter, and schema description coverage is 100% ('A company number or employer name'), so the schema already carries the semantics. The description adds no disambiguation between the number and name forms or their format expectations, 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?

States a specific verb (read and benchmarked) and resource (an employer's gender pay gap reports), and enumerates the distinct output facets - median/mean gaps, bonus gaps, pay quarters, YoY trend, rank. Among siblings such as public_record, company_search and payment_practices, no other tool covers statutory gender pay gap reporting, so it is clearly distinguishable.

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 or when-not-to-use guidance and no named alternative. It does not tell the agent whether to resolve an employer first via company_search or what happens for an employer that has never filed a report.

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