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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior. The description adds real context beyond them: the values are advertised (not actual) salaries, restricted to remote jobs, and denominated in USD. It says nothing about aggregation windows, freshness, or pagination.

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 sentence with no filler; the optional-category caveat is appended efficiently. It is terse rather than padded, though it errs slightly toward under-specification.

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 a read-only, zero-required-parameter insights tool with no output schema, the description conveys scope (remote, USD, by category) adequately. An agent could still want to know the shape of the returned ranges and whether it is a global or per-category aggregate, but nothing essential to invocation 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 100% and the single parameter's description points to list_categories, so the schema does the heavy lifting. The description's "optionally for one category" merely restates optionality already encoded by the empty required list.

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 (advertised salary ranges) and narrows it to remote jobs in USD by category, which is more precise than the bare tool name. It lacks an explicit verb (list/retrieve), but the noun phrase unambiguously describes the payload. Sibling get_statistics could plausibly overlap, and nothing here distinguishes 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?

"optionally for one category" tells the agent the parameter is optional but gives no when-to-use guidance relative to get_statistics or the other retrieval tools. There is no statement of prerequisites or exclusions.

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