inject_spikes

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

With no annotations and no descriptive content, the tool's behavior is completely undisclosed. The description offers no information about effects, side effects, required permissions, or return values.

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 text is extremely short, but this is under-specification rather than conciseness. Every sentence is absent; the description is merely a title with no useful content.

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 complexity of the neural simulation context, a large sibling set, and a parameterized schema, the description is wholly inadequate. It provides no operational context, usage intent, or integration guidance.

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 description coverage is 0% and the description adds zero semantic information about the two parameters (neuronIds, strength). The agent receives no help understanding their meaning or relationships.

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 'Spike Injection' is a tautology of the tool name 'inject_spikes.' It fails to specify the verb-resource relationship or differentiate this tool from siblings like np_send_trigger or np_count_spikes. No actual purpose is stated.

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?

There is no guidance on when to use this tool versus the many sibling tools related to spikes and neural processing. No context, prerequisites, or exclusions are provided.

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