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

Beyond the readOnly/destructive annotations, it discloses real behavioral traits: data comes from employers' own careers sites, is rebuilt daily, is free, and no employer is named in the output. Missing pagination or result-volume expectations, but the provenance and freshness disclosure is meaningful added context.

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?

Front-loaded and information-dense, but the first sentence is an unwieldy run-on that re-enumerates fourteen job categories already listed in the occupation parameter description. That duplication is waste in an otherwise tight definition.

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 carries the return-value explanation and does so adequately by naming the fields returned (postings, employers hiring, pay range, employment type). It could be slightly more explicit about result granularity or volume, but an agent can call it correctly.

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%, so the baseline is 3, but the description adds practical value with concrete occupation phrasing examples ("registered nurse", "truck driver", "warehouse") and confirms state accepts a code, a name, or the US default. That reduces format ambiguity the schema leaves open.

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 states a specific resource and scope: live postings, employers hiring, posted pay range and employment type for one occupation, nationally or in one state. It distinguishes itself from request_competitive_hiring_report, but sibling tools like hiring_signals and job_openings_index sound overlapping and are never differentiated.

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 gives clear usage context (one occupation, national or single state, plain-word occupation phrasing) and explicitly routes the agent to request_competitive_hiring_report when per-employer detail, time-to-close, or requirements are needed. It offers no guidance on when hiring_signals or job_openings_index would be the better choice.

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