snn_reset

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

With no annotations provided, the description must fully disclose behavioral traits. 'Reset SNN Engine' is too vague; it doesn't mention side effects (e.g., data loss), authorization needs, or impact on other components. The agent cannot assess safety or reversibility.

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 sentence, which is concise, but it could convey more meaning without extra length. It is not front-loaded with the most critical information, though brevity is a positive.

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 potential impact (resetting an engine), the description is incomplete. It does not explain what happens after reset (e.g., state restoration, logging), nor does it provide output schema context. More detail is needed for an agent to use it correctly.

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?

No parameters exist, so the description does not need to explain them. Schema coverage is trivially 100%. Baseline for zero-parameter tools is 4; no additional information is required.

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' clearly identifies the action (reset) and resource (SNN Engine), but lacks specificity on what 'reset' entails—e.g., state reinitialization, parameter clearing, or full system restart. Among siblings like tcai_reset, no differentiation is provided.

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 on when or why to use this tool versus alternatives. The description does not state prerequisites, exclusions, or typical scenarios, leaving the agent to guess appropriate invocation context.

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