get_snn_state

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

No annotations are present, and the description only says 'SNN Engine State' with no disclosure of behavior, side effects, return format, or whether it is a safe read. Since annotations are absent, the description carries the full burden and fails to provide any behavioral context.

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 short but under-specified, not genuinely concise in a helpful way. It lacks a verb and substantive content, so the brevity does not aid an agent in selecting or invoking the 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?

For a zero-parameter tool with no output schema and no annotations, the description should state what state is returned or how the result can be used. 'SNN Engine State' only labels the tool, leaving the agent without information about return values, scope, or purpose.

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 0 parameters and the input schema is empty, so there are no parameter semantics to clarify. With a zero-parameter tool, the description is not required to add parameter-level detail, so the baseline of 4 applies.

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?

Description 'SNN Engine State' is a noun phrase that restates the tool name ('get_snn_state') without a clear verb or explanation of what the tool does. It does not distinguish what 'state' means or how it differs from sibling tools like get_system_status or get_metrics.

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 about when to use this tool vs alternatives. The sibling list contains many state/status tools (get_system_status, wm_status, np_status), but the description gives no context, prerequisites, or exclusions.

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