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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety and access profile is covered. The description adds only a liveness signal ('whether it still looks live'), which is the one useful non-annotation hint; it says nothing about auth, rate limits, or freshness guarantees, and most of the sentence restates return contents.

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 sentence that front-loads the action and scope with no filler. The trailing return-value list is slightly awkward phraseology but does not bloat the text.

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 single-parameter read tool with an output schema and full annotation coverage, the description covers purpose and input provenance adequately. Its gap is the missing differentiation from the sibling 'get_job', which is the one thing an agent still needs.

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 schema already documents 'id' as 'a result id from search'. The description's 'by an id search returned' reinforces the provenance but adds no format, validation, or nominal-vs-internal distinction beyond the schema, so the baseline 3 applies.

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 posting in full') plus the identifier source, so the job is unambiguous. It does not, however, differentiate itself from the sibling 'get_job', which by name appears to do something very similar.

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?

Usage is implied by 'by an id search returned', which tells the agent the id must come from a prior search step. There is no explicit when-to-use/when-not guidance and no routing against 'get_job' or 'search_jobs', leaving the agent to guess which retrieval tool to pick.

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