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

Beyond the readOnly/openWorld annotations, the description discloses several behaviors an agent could not infer: access goes through a residential proxy, only the three reviews shown to logged-out visitors are returned, and the call costs $0.002 in USDC via x402 (Base, Solana or Arc) with failures not charged. These are exactly the operational facts that affect selection and planning.

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?

One dense paragraph that front-loads what the tool returns before moving to input requirements and pricing. Every sentence carries information, though the run-on field list is slightly heavy.

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, annotations covering safety, and a fully documented single parameter, the description fills the remaining gaps: input identifier shape, payment model, proxy routing, and the truncation of reviews. Nothing an agent needs to call it correctly is missing.

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 already 100%, so the baseline is 3. The description reinforces the single parameter's format ('Apple-E1138') and pairs it with a concrete example, adding modest but real confirmation of the URL-slug form.

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 names a specific resource (Glassdoor employer reviews) and enumerates exactly what comes back: overall rating, sub-ratings, CEO approval, recommend/outlook shares, star distribution and three sample reviews. That makes clear it is a reviews endpoint rather than a job-listings endpoint, though it never explicitly contrasts itself with the similarly named sibling jobs_glassdoor_jobs.

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?

It states the prerequisite input ('Needs the employer's Glassdoor name and id, e.g. Apple-E1138'), which is useful context. But it offers no when-to-use/when-not guidance and never routes the agent to a sibling such as jobs_glassdoor_jobs when listings rather than reviews are wanted.

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