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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered for free. The description adds only the shape of the returned data (state, money state, acceptance summary); it says nothing about visibility/permission scope, failure modes for an unknown or unauthorized jobId, or whether money state can be stale.

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?

Two short clauses, front-loaded with the resource and the return payload. The trailing "Needs jobId" is largely redundant with the schema's required list, a small amount of 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?

There is no output schema, so the description is the only source for return-value structure, and it provides just three terse field names with no types or shape. For a read tool whose annotations carry the safety profile this is workable, but an agent cannot reliably predict the response format.

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 50%: apiKey is documented in the schema but jobId has no description at all. "Needs jobId" merely restates the required array and gives no format, origin (e.g., returned by post_job or apply_job), or error behavior for an invalid id, so the description does not compensate for the gap.

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?

States a specific verb and resource ("Read one job") and names the payload it returns (state, money state, acceptance summary), which distinguishes it from list_jobs at a glance. It stops short of explicitly contrasting with siblings, so not a 5.

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?

"Read one job" implies the single-record case versus list_jobs, and "Needs jobId" signals the lookup key, but there is no explicit when-to-use/when-not or named alternative. Usage must be inferred from the name and the presence of list_jobs.

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