cleanup_stale_rooms

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

With no annotations, the description must disclose behavioral traits. It states 'clean up' but does not specify whether this involves deletion, archiving, or other actions. The presence of a dryRun parameter suggests potential destructiveness, but this is not articulated.

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 concise sentence, but it is too brief to be maximally useful. It could benefit from more detail while remaining concise.

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 complexity of 6 parameters and no output schema or annotations, the description fails to provide sufficient context about return values, side effects, or prerequisites. For example, it does not indicate what the tool returns (e.g., list of cleaned rooms) or how the dryRun mode works.

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?

All 6 parameters have descriptions in the input schema, providing full coverage. The description adds no additional meaning beyond the schema, so it's adequate but not improved.

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 identifies the verb 'clean up' and resource 'stale rooms', and mentions criteria. However, it is somewhat generic and does not differentiate from other cleanup tools like 'cleanup_stale_agents' or 'run_comprehensive_cleanup'.

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 provided on when to use this tool versus alternatives. There are many sibling cleanup tools, but the description does not specify when to choose this one over others like 'cleanup_orphaned_projects' or 'run_comprehensive_cleanup'.

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