Hedgehog

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

With no annotations provided, the description carries the full burden but only minimally hints at return format ('summary information'). It lacks disclosure on safety (read-only vs mutable), performance characteristics of listing 'all' items, or what specific fields the summary includes.

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 is appropriately front-loaded and wastes no words, though it borders on under-specification given the complex sibling ecosystem.

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 a zero-parameter list operation with existing output schema, but given the presence of spike_archive and spike_get_state siblings, it should clarify whether 'all' includes archived or completed investigations.

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?

Zero parameters with 100% schema coverage meets the baseline score of 4 per the rubric. No parameter description is necessary.

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 verb (List), resource (spike investigations), and scope (all with summary information). The mention of 'summary information' distinguishes it from sibling spike_get_state which likely retrieves detailed single-item state.

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 use this versus alternatives like spike_get_state, nor does it mention prerequisites, filtering limitations, or pagination behavior despite claiming to return 'all' investigations.

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