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

No annotations are provided, so the description carries the burden. It discloses that the response includes the full description text and HTML and that the id comes from an earlier result, but it does not mention error behavior, authentication, rate limits, or confirm the read-only nature beyond the word 'Fetch'. This is adequate but not rich.

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 three sentences, front-loaded with the core purpose, followed by precise usage context and a source note for the parameter. Every sentence adds necessary information with no fluff or redundancy.

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?

This is a simple single-parameter read tool with an output schema present. The description covers what it does, how to obtain the id, and when to use it relative to sibling tools. Nothing critical is missing for an agent to call it 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?

The input schema already provides 100% coverage with the description 'Roleset job id (UUID) from an earlier result.' The tool description repeats this without adding new semantic details, so it stays at the baseline for full schema coverage.

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 action and resource: 'Fetch a single posting by its Roleset id, including the full description text and HTML.' The word 'single' and the focus on a unique identifier clearly distinguish this from sibling listing/search tools like search_jobs, job_changes, and company_jobs.

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 explicitly says when to use this tool: 'Use after search_jobs or job_changes when you need the body of a specific posting'. It names the preceding sibling tools and gives concrete use cases, but does not explicitly state when not to use it (e.g., when only metadata is needed).

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