np_send_trigger

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it fires triggers/executes StimParams, but it does not disclose side effects, irreversibility, hardware implications, or return behavior. This is a significant transparency gap for an action-oriented tool.

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, tightly packed sentence that states purpose upfront with no filler. It communicates the tool's identity and function efficiently.

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?

The tool is simple with fully described parameters, but the description lacks usage guidance and behavioral effects. Since there are no annotations and no output schema, the overall context is minimally viable but has clear gaps in when to use and what to expect.

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 100%, so the baseline is 3. The description adds extra meaning by clarifying that the triggers use a '16-bit trigger array', which explains the 0-15 range for trigger values and frames them as bit positions. This goes beyond the schema's simple 'trigger keys' description.

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 clearly specifies the action ('Fire trigger(s)') and the resource ('execute uploaded StimParams via a 16-bit trigger array'). It distinguishes the tool from siblings like np_count_spikes, np_query_triggers, and np_configure_stim by stating that this tool executes/fires rather than queries or configures.

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 implies usage in the context of having uploaded StimParams and wanting to execute them, but it does not explicitly state when to use this tool versus alternatives. No when-not-to-use or alternative tools are mentioned, so guidance is implied rather than explicit.

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