archive_spools

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

No annotations are provided, so the description must convey behavioral impact. It states the precondition (empty status) but does not disclose side effects, reversibility, permissions, or handling of invalid inputs. For a mutation tool, this is a significant gap.

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 exceptionally concise: one sentence for the purpose and one line for the parameter. Information is front-loaded, with no filler or redundant details.

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?

With an output schema present and a simple single-parameter operation, the description covers the basic action and precondition. However, it omits behavioral details like whether archiving is reversible or what happens to associated data, leaving a notable gap for a mutation tool.

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 schema provides only the parameter name and type with no description. The description explains that spool_ids is a list of spool IDs to archive and adds the constraint that they must have 'empty' status, adding meaning beyond the raw 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 uses a specific verb 'archive' with resource 'empty spools', clearly distinguishing from sibling tools like mark_spool_empty or open_spool. The 'bulk' qualifier clarifies it operates on multiple spools at once.

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 requirement that spools must have 'empty' status provides a clear precondition, but the description does not explicitly state when to prefer this tool over alternatives or what happens with non-empty spools. Usage context is implied rather than explicitly contrasted with siblings like mark_spool_empty.

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