run_comprehensive_cleanup

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

No annotations provided, so description must disclose behavior. It states 'cleanup' but does not explain what happens to agents/rooms (deleted, archived, etc.), nor the detailed reporting format. Does not mention side effects or authorization needs.

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, no wasted words, front-loaded with key verb and scope. Could be slightly more informative, but remains 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 4 parameters combining two domains and no output schema, description lacks explanation of cleanup behavior, dry run meaning, and reporting specifics. Does not mention sibling tools for reference.

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 4 parameters have detailed schema descriptions (100% coverage), so baseline is 3. The description does not add additional parameter context beyond the high-level purpose.

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?

Description clearly states it runs comprehensive cleanup for both agents and rooms with detailed reporting, using a specific verb+resource. It distinguishes from sibling tools like cleanup_stale_agents or cleanup_stale_rooms which are more narrow.

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 on when to use this vs. narrower sibling cleanup tools. Description does not mention scenarios, prerequisites, or when to avoid using it.

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