inject_stealth_to_workers

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

Discloses default preset, watch behavior subscription, and session scope. However, with no annotations, it lacks details on side effects, reversibility, or permissions needed.

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 concise sentences with no unnecessary words, front-loading the core action and then the watch option.

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?

Given no output schema and simple parameters, the description covers the main functionality and optional behavior. Could mention return value (likely void) but adequate.

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?

Adds meaning by clarifying defaults (preset default Firefox-default, watch default true) but does not explain valid preset values or full behavior beyond defaults.

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 states the action: push a stealth preset into every dedicated/shared worker realm via post-start eval. It distinguishes from siblings by specifying the target (workers) and mechanism.

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?

Implies usage for injecting stealth into workers but provides no explicit guidance on when to use this tool versus alternatives like inject_stealth or inject_stealth_hook.

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