get_snn_state

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states 'SNN Engine State,' which implies a read operation but does not explicitly confirm read-only behavior, required permissions, or potential side effects. The lack of detail makes it insufficient for an agent to understand implications.

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 concise at three words, which is efficient for a simple tool. However, it is so minimal that it adds little value beyond the tool name. Structure is adequate but could benefit from additional context to earn its place.

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 role as a state retrieval mechanism and the absence of an output schema, the description fails to specify what data the state contains or how it differs from sibling tools like get_platform_status. The context is incomplete for an agent to reliably distinguish usage.

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 description need not add meaning to parameters. Per calibration, a baseline of 4 applies when no parameters exist. The description does not contradict this baseline and is adequate for the parameterless context.

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 'SNN Engine State' clearly indicates the tool retrieves the state of the SNN engine, establishing a specific verb-resource pair. However, it does not differentiate from sibling tools like get_platform_status or get_system_status, which also retrieve states. The description is minimal and borders on tautology.

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 get_metrics or snn_reset. There is no mention of context, prerequisites, or exclusions, leaving the agent without clear usage boundaries.

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