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

Annotations already declare readOnlyHint=true, so safety is covered elsewhere. The description adds genuine behavioral context by disclosing the sort order ('newest first'), but says nothing about volume, pagination, or whether results are scoped to the caller.

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?

Four words, front-loaded with the resource and immediately followed by the ordering constraint. It is efficient, though so terse that 'List' is only implied rather than stated.

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 zero-parameter list tool with annotations covering safety, little is strictly required. Still, the absence of any note on result size, pagination, or ordering stability leaves real gaps an agent would hit on a large job set.

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 tool takes zero parameters, which is the baseline-4 case. 'All jobs' usefully confirms there is no filtering, though it does not say whether the result set is capped.

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 names the resource (jobs) and implies the list verb, and 'newest first' gives ordering. But it never states what a 'job' is or how this differs from sibling get_job or call_api, so the purpose is only minimally clear.

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?

There is no guidance on when to call this versus get_job, create_job, or undo_job in the sibling list. The agent must infer that this is the enumeration path rather than a single-item fetch.

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