np_configure_stim

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

No annotations are provided, so the description carries full burden. It mentions 'validate' and 'upload' but does not disclose validation criteria, error behavior, or any safety or mutation details. The phrase 'charge-balanced biphasic' adds some behavioral context but is insufficient.

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?

Single sentence, front-loaded with action verbs, no unnecessary words. Every element contributes to understanding the tool's purpose.

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?

Despite having 11 parameters and no output schema, the description is extremely brief. It omits return values, prerequisites (e.g., platform connection), side effects, and post-upload behavior. Given the tool's complexity, this is insufficient.

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?

With 82% schema description coverage, the schema already documents most parameters. The description adds the conceptual context of a 'StimParam', but does not provide additional meaning beyond the schema's descriptions (e.g., units are already in schema).

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 specific verbs 'Define, validate & upload' and explicitly names the resource 'StimParam' with the qualifier 'charge-balanced biphasic stimulation'. This clearly distinguishes the tool from siblings like np_send_trigger or np_count_spikes.

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 (configure stimulation parameters before sending triggers) but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools for similar tasks.

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