snn_step

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

With no annotations, the description must disclose behavioral traits. It only says 'Advance', which implies a forward time step, but does not clarify side effects (e.g., resets or triggers), required permissions, or whether the simulation state is mutated permanently.

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 very short, which might be efficient if complete, but it omits critical context. It is under-specified rather than concise; key information about parameters and behavior is missing.

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 simple single-parameter schema and no output schema, the description should cover at least the effect of advancing and the role of 'steps'. It does not, leaving gaps about the tool's behavior and output.

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 input schema has one parameter 'steps' with constraints, but the description does not mention it. Schema description coverage is 0%, so the description adds no meaning beyond what the schema already provides, which is a missed opportunity.

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' clearly indicates the action and resource, but it lacks specificity. It does not distinguish this tool from siblings like snn_reset or simulation_control, leaving the agent unclear about what 'advance' entails.

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 guidelines are provided about when to use this tool versus alternatives. The description does not mention prerequisites, typical use cases, or suggest other tools like simulation_control for different scenarios.

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