Clean Workspace

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

Without annotations, the description indicates a destructive action and returns a summary, but omits details like irreversibility, permission requirements, or side effects (e.g., cascading deletes). This is adequate but not thorough.

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 sentences front-load the key information: what it does (delete workspaces), modes (by ID or age), and what it returns. 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?

For a 2-parameter tool with no output schema, the description explains the return value (summary) and basic behavior. It is fairly complete, though it could mention that deletion is irreversible.

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%, and the description adds context: workspaceId is optional and triggers age-based cleaning; olderThanHours is a safety filter. This enhances understanding beyond 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 the tool deletes test workspaces and associated history, with two distinct modes: by ID or by age. This distinguishes it from sibling tools like get-test-workspace or list-workspaces.

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 explains when to use each mode (specific ID vs. cleaning old workspaces), but does not explicitly state when not to use it or mention alternative tools like list-workspaces for inspection.

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