list_jobs

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

With no annotations, the description fully discloses key behaviors: result size, truncation risk, and workarounds (summary, file processing). No contradictions, and it adds actionable information beyond the 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?

Two short paragraphs: first states purpose, second provides a critical warning and action. Every sentence is valuable, though the warning could be slightly condensed. Front-loaded with purpose.

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?

Output schema exists, so return values are documented. The description covers the most important behavioral context (size, truncation). However, it lacks any parameter-level guidance, which is a significant gap given 15 parameters and 0% schema coverage.

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 has 0% description coverage for 15 parameters. Description only mentions the summary parameter (value true/false) without details. Does not explain other parameters like ids, arch, test, etc., meaning the description adds almost no semantic value to 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 clearly states 'List jobs matching the given filters.' with a specific verb and resource. It distinguishes from siblings like list_jobs_overview by mentioning the summary parameter for compact output.

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?

Provides clear context: warns about large results (1.5 MB, 150+ jobs) and potential truncation, suggests using summary=True for triage or saving to file for full data. Does not explicitly compare to alternatives like list_jobs_overview, but offers practical usage guidance.

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