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

Beyond the annotations, the description reveals that this is an asynchronous, queued operation rather than a synchronous launch, and that it depends on the extension being active and connected. It also discloses that the return value is a command id, which is useful because no output schema is present.

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?

Two sentences front-load the core action and return behavior, then add the prerequisite, monitoring, and stopping guidance without redundancy. Every phrase contributes useful information.

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 complex 12-parameter tool with no output schema, the description covers the essential launch-monitor-stop workflow, the async pickup model, and the environment prerequisites. Detailed parameter semantics are appropriately left to the richly described schema, though the description could improve by acknowledging the related open_launcher and stop siblings.

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 input schema already documents each parameter. The description adds a high-level mapping of mission types to outputs, but this largely restates what the mission and sink enum descriptions already say, so it does not exceed the schema baseline.

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 states a specific action — queue a browser mission for the user's Neuron extension — and names the two possible outcomes: mining content into a Collection or prospects into the lead pool. It also differentiates itself from sibling monitoring and control tools by naming neuron_webagent_list_runs, neuron_webagent_get_run, and neuron_webagent_kill as follow-up operations.

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?

It gives clear operational context: the mission is queued and picked up on the next extension poll, so the browser must be open, signed in, and remote-control enabled. It names monitoring and stopping alternatives, though it does not explicitly state when a sibling such as neuron_webagent_stop or neuron_webagent_open_launcher should be preferred.

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