np_send_trigger

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

No annotations are provided, so the description must disclose side effects, but it only mentions 'execute uploaded StimParams' without clarifying whether triggers have lasting effects, need pre-uploaded params, or what happens on invalid input. It also inaccurately calls the 0-15 range a '16-bit trigger array'.

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 with no filler, front-loading the verb 'Fire'. It is concise but arguably too sparse, missing relationships to other NP tools.

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?

With no output schema, no annotations, and two parameters, the description should explain prerequisites (uploaded StimParams), potential physical effects, and how this tool fits with np_configure_stim and np_query_triggers. It does none of this, leaving the agent without enough context to use it safely.

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?

Both parameters have schema descriptions, so baseline is 3. The description adds minimal value, only hinting that triggers map to a 16-bit array, but the schema already explains trigger keys and repeats. The 16-bit terminology is misleading since max is 15.

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 uses a specific verb 'Fire' and identifies the resource 'trigger(s)' and the effect 'execute uploaded StimParams via a 16-bit trigger array'. This distinguishes it from query tools like np_query_triggers, though it doesn't explicitly name any sibling.

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 when-to-use or alternative guidance is given. The description only states the function, not when to prefer this over np_configure_stim or np_closed_loop.

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