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

Goes well beyond the annotations (which only cover read-only/idempotent/no-destructive safety): it discloses ordering stability semantics (result_position is stable saved-search order, display_rank may change), warns that relevance_score is an automated hint and not verified candidate fit, states the required auth scope (jobs:read), and notes there is no credit charge.

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?

Front-loaded with the core action, then dense telegraphic clauses with no filler; every sentence carries distinct information (stability, ranking caveat, ID preservation, scope, cost). The clipped style is efficient but borders on terse, with several facts packed into adjective-less fragments.

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 describes the return shape's semantics (result_position, display_rank, relevance_score, job_id/search_id) and covers auth, cost, and paging stability. Remaining gaps are cursor mechanics and any explicit page_size guidance, so it falls short of fully complete rather than being deficient.

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 description coverage is 0% and the description only partially compensates: it implies search_id's role via 'explicit search' and 'preserve ... search_id', and 'bounded page' loosely gestures at page_size. The critical cursor parameter — how to obtain and pass it to advance pages — is entirely undocumented anywhere, which is the single most important mechanic for a paginated list tool.

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 — reading a bounded page of results from an explicit search — and pins the scope with 'even after another search', which distinguishes it from re-running a search. It does not name sibling tools like search_jobs or load_more_jobs, so the differentiation is implied by behavior rather than explicit.

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?

Gives clear usage context: this is the tool for re-reading a page of an existing search without reissuing it, and it instructs the agent to preserve job_id/search_id for follow-ups. However, it never states when NOT to use it or names the alternative (search_jobs, load_more_jobs) for those cases.

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