snn_reset

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

With no annotations, the description carries full behavioral burden. 'Reset SNN Engine' discloses no side effects, state changes, whether it is destructive, or what the tool actually resets. For a mutation-like operation, this is a critical transparency 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 a single concise sentence, front-loaded with the essential action. It is efficient, though possibly too sparse to fully inform an agent, but it earns a good score for brevity.

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 tool's likely side effects and lack of annotations or output schema, the description is insufficiently complete. It does not explain what state the SNN engine resets to, what is cleared, or what the agent should expect, leaving the agent without essential context.

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 tool has zero parameters, so the baseline of 4 applies. The description adds no parameter information, but none is needed; the empty schema already fully covers the absence of parameters.

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 'Reset SNN Engine' uses a specific verb and resource, clearly indicating the action on the SNN engine. It distinguishes from siblings like snn_step and get_snn_state, though it does not explicitly contrast with tcai_reset, leaving minor ambiguity among reset tools.

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 description provides no guidance on when to use this tool versus alternatives such as snn_step or get_snn_state. No context, prerequisites, or exclusions are given, leaving the usage conditions entirely unclear.

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