cortex_cleanup_jobs

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

No annotations are provided, so the description must fully convey behavioral traits. It mentions deletion but omits critical safety details such as the existence of the 'dryRun' parameter (default true) which prevents accidental loss. This gap in transparency is significant for a destructive operation.

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?

The description is exceptionally concise at two sentences with no filler. It front-loads the action and purpose, making it easy for an agent to parse quickly.

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?

Given the tool's destructive nature and 4 parameters, the description lacks sufficient context. It does not explain deletion logic, safety mechanisms (dryRun), or behavior of the limit parameter. An output schema is absent, and the description fails to compensate.

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%, so the schema already describes each parameter with basic explanations. The description adds 'by status or age' but does not clarify how parameters interact (e.g., AND/OR logic) or provide deeper semantics beyond the schema defaults.

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 the verb 'Delete', the resource 'jobs', and the scope of 'multiple jobs by status or age'. It distinguishes from sibling tools like 'cortex_delete_job' which handles single job deletion, making its purpose unambiguous.

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?

The description advises using the tool for 'cleaning up failed or old jobs', providing clear context on when it is appropriate. However, it does not explicitly state when not to use it or mention alternatives beyond the implied context of cleanup.

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