sc:cleanup

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

No annotations provided; description only mentions cleanup and debt reduction without disclosing behavioral traits like destructiveness, side effects, or permissions. Flags like --unused suggest deletion but not confirmed.

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 plus parenthetical is extremely concise, front-loading key info with zero waste.

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?

No output schema, yet description fails to explain return values or what happens after cleanup. Lacks context on effects or outcomes.

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 baseline is 3. Description adds no additional parameter context beyond schema descriptions.

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 the tool is for project cleanup and technical debt reduction, with category and priority. However, it does not explicitly distinguish from siblings like sc:improve.

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?

Implies usage through 'maintenance' category and 'RECOMMENDED' priority, but lacks explicit when-to-use, when-not-to-use, or alternatives guidance.

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