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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds non-obvious behavior: Cloudflare + PerimeterX anti-bot handling is done for the caller, paging collects up to max_results across pages, `date` sort includes sponsored placements, and the cost model is one billing unit per fetched result page. Only retry/error and rate-limit behavior remain unstated.

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?

A single front-loaded paragraph that leads with what is searched and returned before filters and cost. It is densely packed with useful content, though "Returns JSON." is redundant with the opening "returns the job listings as JSON" and could be dropped.

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?

For an 11-parameter, no-output-schema tool, the description covers the return shape, filtering, pagination, sorting, anti-bot handling, and cost, which is most of what an agent needs to call it correctly. It omits failure modes (blocked requests, zero results) and pagination resume behavior via `start`.

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?

With 100% schema coverage the baseline is 3, but the description goes beyond the schema by clarifying that `days` is posting age, that `sort=date` returns collected jobs newest-first including sponsored ones, and that `max_results` is accumulated across pages rather than a single-page size. That is real added meaning for the two least obvious parameters.

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 concrete verb+resource ("Searches Indeed for `query` in `location` and returns the job listings as JSON") and enumerates the returned fields, so an agent can immediately tell this is the Indeed job-listing tool rather than the google_search, amazon_search, or zillow_search siblings.

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 names the available filter knobs (country, job_type, days, remote), the sort options, and gives an explicit operational constraint: "keep max_results modest" because listing plugins bill one unit per result page. It does not state when to prefer this over a general web search or when results are unavailable, so there are no explicit exclusions.

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