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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: closed/stale postings are still returned and the caller must inspect status before acting. It stops short of covering unknown-id behavior or error responses.

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 compact sentences with zero filler, and the payload summary is front-loaded ahead of the staleness caveat. Every clause carries information an agent can act on.

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?

An output schema exists, so return-shape explanation is not required, and the annotations cover the safety profile. For a one-parameter read tool the description is nearly complete; the remaining gap is the absence of any guidance on missing/invalid ids or on pairing with search_jobs for discovery.

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?

There is a single required parameter, 'id', whose name and UUID format in the schema make its meaning largely self-evident, and the description implies it selects 'a posting'. However, with 0% schema description coverage the description could have stated explicitly that the id is a job/posting identifier rather than something else, so it adds only marginal meaning.

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 uses a specific verb ('Read') with a specific resource ('a posting') and enumerates what comes back: catalog status, description, and the original application link. That makes it clearly a single-record fetch, distinguishable in spirit from search_jobs, though it never names the sibling explicitly.

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 one concrete usage instruction — 'check status before recommending' — which tells the agent how to act on the returned data. Beyond that, when-to-use is only implied by the read-a-posting phrasing; there is no explicit routing to search_jobs for discovery and no conditions under which this tool should be skipped.

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