List Jobs

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

No annotations are supplied, so the description carries the full burden and does almost nothing with it. It does not disclose result ordering (newest first?), the time window implied by "recent", pagination limits, or the default page size, all of which materially affect how the tool behaves.

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?

Two words are certainly front-loaded, but here brevity comes from under-specification rather than efficiency. The sentence is clean yet carries almost no information an agent could act on.

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?

An output schema exists, so return values need not be explained. But for a list tool with an undocumented limit parameter and no annotations, the description should at least define "recent" and describe result ordering and volume — none of which it does.

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 schema description coverage is 0%, so the lone `limit` parameter is undocumented everywhere. The description never mentions the parameter, its default of 20, or any maximum, so it fails to compensate for the schema gap.

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?

"List recent jobs" names a specific verb (List) and resource (jobs), so the basic action is clear. However, "recent" is never defined and there is no differentiation from siblings like get_job (single job retrieval) or diff_jobs (comparison), which an agent must infer on its own.

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 when-to-use guidance, no statement of what selects this over get_job or diff_jobs, and no prerequisites or exclusions. The agent is left to guess the routing logic entirely.

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