snn_reset

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'Reset SNN Engine' does not mention whether the operation is destructive, what state is affected, whether it requires specific permissions, or any side effects. For a reset tool, this is a significant omission.

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 extremely brief but under-specifies the tool's behavior. It is a fragment ('Reset SNN Engine') rather than a complete sentence, and conciseness here reflects lack of content, not efficient writing.

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 purpose (a reset operation), the description is incomplete. It does not explain what happens when the SNN engine is reset, what data is cleared, or whether the operation is reversible. Even with no parameters, behavioral context is essential and missing.

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 there is nothing to describe beyond the schema. The description does not add parameter-related meaning, but the baseline of 4 applies because no parameters exist.

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 states 'Reset SNN Engine,' which specifies a verb and resource, making the basic purpose clear. However, it does not elaborate on what 'reset' means (e.g., clearing weights, state, or configuration) and does not distinguish from sibling tools like tcai_reset beyond 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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites or contextual indicators. The description is purely a statement of the action with no usage direction.

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