Hedgehog

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

With no annotations, description carries full burden. 'Move to archive directory' clarifies the physical action (distinguishing from deletion), but lacks critical safety context: reversibility, whether references break, required permissions, or side effects on sibling operations like spike_list.

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?

Front-loaded purpose statement followed by Args block. Every sentence earns its place—no redundancy or generic fluff. Appropriate length for a single-parameter tool.

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?

Adequate for the mechanical operation (given output schema exists), but incomplete for the rich spike workflow ecosystem. With 15+ sibling tools, description should clarify archival's role in the lifecycle (e.g., final state vs. reversible). Parameter documentation saves it from being inadequate.

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 0% (only title 'Name' with no description). Description compensates effectively by documenting 'name' as 'Spike name to archive', clarifying the parameter's semantic domain that the schema omits.

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?

Clear specific verb ('Archive') and resource ('spike investigation') with helpful parenthetical clarification ('move to archive directory') that distinguishes it from deletion. However, lacks explicit differentiation from sibling tools like spike_delete or spike_complete_branch.

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 no guidance on when to archive vs. delete, complete, or mark as dead end. No mention of prerequisites or whether archived spikes can be restored. Agent must infer usage from the ecosystem context.

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