archive_idle

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

With no annotations, the description carries the full behavioral burden. It states 'Never silent-deletes' and mentions 'recoverable path,' explicitly disclosing the non-destructive, reversible nature of the operation.

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 three concise sentences with no redundant or vague language. Each sentence adds specific value: what the tool does, how the default works, and how to trigger the actual action with a safety note.

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 simple parameter set, the description covers the tool's behavior, default mode, explicit action trigger, and a key safety guarantee. No output schema is needed, and no additional context appears necessary for correct invocation.

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 single parameter 'apply' is fully described, including its boolean effect and default value (false = dry-run). Schema coverage is 100%, and the description adds meaningful context beyond the schema type.

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?

Clearly states the tool lists idle and shadowed user-tier skills and, with apply:true, archives them. The verb 'List' plus the archive action are both explained, making the purpose unambiguous despite the name.

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?

Provides explicit usage instructions: default dry-run reports what would move, and apply:true triggers the archive. Lacks an explicit comparison to sibling tools, but the self-contained guidance is sufficient for a user to know when and how to invoke it.

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