jobs_purge

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

Discloses destructive behavior and the order of operations (terminate active runners before purge). No annotations provided, but description does not cover reversibility, logs, or artifacts. Adds moderate value beyond the name.

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?

Single sentence of 13 words, front-loaded with action and object. No wasted words.

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?

Provides core purpose but lacks details on return value, confirmation, or side effects. Adequate for a simple destructive tool but could be more comprehensive given no output schema or annotations.

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 coverage is 100% with project_id already described. Description adds no additional parameter detail, so it meets baseline but does not enhance understanding.

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?

Clearly states the action ('Purge') and resource ('all managed job runs for a project'), with additional detail about terminating active runners first. Distinguishes from sibling tools like jobs_cancel and jobs_submit.

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?

Implies usage for cleaning up all job runs in a project, but does not explicitly state when to use versus alternatives like jobs_cancel. No when-not or prerequisite guidance.

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