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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this returns a single listing's full text with specific fields, which is useful, but it says nothing about failure behavior for an unknown/expired id or any rate limits.

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 front-loaded sentence that names the resource, the key input, and the payload contents with zero filler. Every clause earns its place.

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?

With no output schema, the description usefully enumerates what comes back (status, dates, reposts, ghost-job flag, description), which an agent needs. It is nearly complete for a one-id read tool, missing only error/edge-case behavior for invalid ids.

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 parameter with 100% schema description coverage ('An id from search.'), so the schema already carries the semantics and a baseline of 3 applies. The description restates that the id comes from search but adds no format, length, or validity details beyond the schema.

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 verb+resource: retrieving 'full text for one listing id' and enumerates the returned fields (status, dates, reposts, ghost-job flag, description). It routes back to 'search' as the source of the id, but never distinguishes itself from the near-identical sibling jobslop_get_job, leaving ambiguity between the two.

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 rather than stated: the id must come 'from search,' so an agent can infer this is the follow-up detail call after a search. However, there is no explicit when-to-use/when-not guidance and no mention of when to prefer jobslop_get_job, jobslop_find_job_by_url, or the bare 'search' sibling.

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