cleanup_preview_runs

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 notes that runs are deleted based on a retention count, but does not disclose whether deletion is permanent, any required permissions, side effects, or what happens to dependent data. This lack of detail leaves the agent uncertain about the tool's impact.

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 a single, short sentence (8 words). While concise, it is under-specified, lacking important details that would make it efficiently informative. It could benefit from a brief explanation of the parameter or expected outcome.

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 has one parameter and an output schema, the description should at least explain the parameter and indicate what the output contains. It does neither, leaving significant gaps about how to use the tool correctly and what to expect from the response.

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 input schema has one parameter, keep_last, with 0% schema description coverage. The description mentions 'beyond a retention count' but does not explicitly link to keep_last or explain its meaning (e.g., number of runs to keep). No default behavior or constraints are clarified, requiring the agent to infer the parameter's role.

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 'Delete older preview runs beyond a retention count' clearly states the action (delete), resource (preview runs), and the selection criterion (retention count). It distinguishes itself from siblings like delete_preview_run (single deletion) and list_preview_runs (listing).

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?

No guidance is given on when to use this tool versus alternatives like delete_preview_run. There are no prerequisites, exclusions, or usage context provided. The description solely states what the tool does without any usage recommendations.

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