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

Annotations establish that this is a read-only, open-world operation, and the description adds material behavioral context beyond them: exact pricing ($0.002 USDC per successful call), payment rails (x402 on Base, Solana, or Arc), and the crucial guarantee that failed calls are not charged. It also discloses the return contents for both listing and detail modes.

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?

The description is front-loaded with the primary retrieval behavior, then the conditional single-job mode, then pricing. Despite being dense, every clause carries operational value, including the payment caveat, and there is no wasted filler.

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?

Given that an output schema exists, the description does not need to exhaustively document return fields, but it still summarizes both listing and posting outputs. With annotations covering safety, schema covering all parameters, and pricing/failure terms explicitly stated, the definition is complete enough for an agent to invoke the tool 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 description coverage is 100%, so every parameter is already documented: company as the Jobvite slug, job as an optional job id from a listing, and q as an optional keyword filter. The description reinforces the company slug pattern (jobs.jobvite.com/<company>) and the job-id mode, but this largely repeats schema content rather than adding new parameter semantics.

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 verb and resource: retrieving open jobs from Jobvite careers sites. It clearly covers both listing and single-posting modes, but it does not explicitly differentiate itself from any sibling tool by name, so it falls just short of the 5 benchmark.

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?

The description gives clear conditional usage: omit the job id to list all open positions with department and location signals, or supply a job id to retrieve that posting's full details. It does not mention when not to use the tool or name alternative sibling tools, so it earns a 4 rather than a 5.

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