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 profile is covered. The description adds genuinely new context: pagination behavior and the concrete field set returned (title, location, company, recruiter, status, workflow ids, dates), which matters because there is no output schema.

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?

Three terse fragments with the resource and returned fields front-loaded and zero filler. 'GET /jobs' is slightly redundant but usefully anchors the tool to the underlying endpoint.

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 no-required-param list tool with full annotation coverage, the definition covers what is returned and that results are paged. The only real omission is routing guidance versus cats_search_jobs / cats_get_job, which is a selection rather than a completeness gap.

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 100% and both parameters (page, per_page) are fully documented with defaults, ranges and next_page chaining. The description's 'Paged' adds no syntax or semantics beyond what the schema already states, so the baseline of 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 (List) and resource (job orders) and enumerates the fields returned, so an agent knows exactly what it gets. It does not explicitly differentiate itself from the close siblings cats_search_jobs or cats_get_job, leaving that inference to the name.

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 only implied: 'List job orders' suggests browsing/unfiltered retrieval, which contrasts weakly with cats_search_jobs. There is no explicit when-to-use, no exclusion, and no pointer to the search sibling among the 30+ alternatives.

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