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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description usefully adds that no API key or gate seat is required, that results are ordered newest first, and that the output matches the REST endpoint. It omits pagination, result limits, and whether the list is ever truncated.

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?

Most of the description is advertising copy about posting costs, featured pricing, hire paths, and directory links, none of which helps an agent decide to call this tool. The one sentence that defines the behavior is placed last instead of being front-loaded.

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 zero-param, read-only listing tool it covers the essential return shape (open jobs, newest first) but stops there, with no pagination or cardinality guidance and no output schema to fall back on. The heavy promotional content occupies space that could have carried this missing operational detail.

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?

The tool takes zero parameters, so the schema-driven baseline of 4 applies. The description adds nothing parameter-related because nothing needs to be supplied, and it correctly presents this as a no-argument call.

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 functional purpose is stated, but only in the second-to-last sentence: "Returns open jobs on the free job board, newest first." That is a clear verb+resource, yet it is buried behind pricing, links, and infrastructure claims. No differentiation from the sibling post_job, which is the obvious counterpart to a job-listing read.

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?

There is no explicit when-to-use guidance. The only directional cues are implicit constraints ("No API key. No Meter look. No Action Gate seat.") and the parity note with GET /api/v1/exchange/jobs, which hints this is the free-tier read path but never says when to prefer it over post_job or another list tool.

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