neuron_grab_media_batch

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

With no annotations, the description carries the burden, and it does disclose the main workflow: opens tabs, extracts streams, downloads, and returns per-URL status/failures. However, it omits side effects like filesystem writes, auth needs, and potential page navigation impacts.

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?

Three dense sentences with no filler. The core action, batch behavior, limit, and return outcome are all front-loaded, and usage context is given at the end.

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?

For a batch download tool with simple, fully documented parameters and no output schema, the description covers the essential workflow and result format. Minor missing details around authentication and filesystem side effects keep it from a 5.

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 coverage is 100%, so the schema already documents all three parameters. The description adds the batch framing and the 5-URL cap, but does not clarify delayMs or outputDir behavior beyond the 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?

States a specific verb and resource ('Download videos from multiple URLs') and clearly indicates batch behavior. The name and description make it distinguishable from the singular neuron_grab_media sibling, though it never names the alternative explicitly.

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?

Provides clear use cases: 'Use for batch downloading from feeds, trending pages, or saved lists.' It does not state when to prefer the singular variant or when not to use the tool, so it stops just short of full routing guidance.

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