snn_step

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

No annotations are provided, so the description alone must disclose behavioral traits. It does not mention side effects, state mutations, destructive actions, or return values. This severely lacks transparency for a tool that likely modifies simulation state.

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, but it is under-specified. Conciseness should not sacrifice informativeness. Every sentence must earn its place; here, the sentence is too minimal to be useful.

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 low complexity (1 optional param, no output schema, no annotations), the description still fails to provide enough context. The effect of the tool, its relationship to other simulation tools, and expected outcomes are not described.

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?

Schema coverage is 0%; the description does not mention the 'steps' parameter at all. While the schema provides min/max/default, the description adds no meaning or clarification about how the parameter affects the simulation.

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 'Advance SNN Simulation' provides a verb and resource, but 'advance' is vague. The parameter 'steps' clarifies that it progresses by a number of steps, but the description doesn't mention this. Purpose is somewhat clear but lacks specificity, leading to ambiguity.

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 to use this tool versus siblings like 'simulation_control' or 'snn_reset'. The description provides no context for appropriate usage, exclusions, or prerequisites.

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