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

Annotations already declare readOnlyHint and openWorldHint, but the description adds materially useful context those don't cover: the metered price ($0.002 USDC per successful call), the x402 payment rails (Base, Solana, Arc), and the fact that failed calls aren't charged. That payment/auth disclosure is exactly the kind of pre-call cost awareness an agent needs. It stops short of stating data recency or coverage caveats, so not a 5.

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, and the domain/purpose is front-loaded ahead of the pricing detail. The first sentence is a dense comma-list of returned fields, which is information-rich but slightly inventory-like rather than structurally organized; still, nothing is wasted.

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 an output schema present, the description needn't spell out return values, and annotations carry the safety profile; the description covers domain scope (US), identifier formats, and cost/payment mechanics. What's missing is any note on data freshness or what happens for unmatched employers, which matters for a paid, open-world lookup.

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 the single 'employer' parameter is already documented with three concrete key examples plus URL support. The description restates the key format ('e.g. Microsoft_Corp') and adds 'or name,' which mirrors rather than extends the schema. Baseline 3 applies since the schema does the heavy lifting.

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 opens with a specific domain and resource: 'US employer pay and benefits from PayScale,' then enumerates exactly what data comes back (benefit types, percentiles, satisfaction, locations). An agent can tell this is a compensation/benefits lookup, distinct from generic company-profile siblings like b2b_linkedin_company_profiles or b2b_similarweb, though it never explicitly contrasts itself with 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?

Usage is only implied by the data inventory — an agent infers it should call this when it needs employer pay/benefits figures. There is no explicit 'use this when…' statement and no named alternative for related needs (e.g., headcount or web traffic, which other siblings cover). The one concrete usability hint is the accepted employer identifier format.

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