inject_stealth

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the mechanism ('via BiDi preload') but does not mention side effects, resource requirements, whether the action is destructive, or if it modifies persistent state. Critical behavioral traits are missing.

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 very short (one sentence), which is concise but lacks structure. It front-loads the main action but omits important contextual details. The brevity comes at the cost of completeness, making it minimally adequate.

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 the tool's complexity (stealth injection, many sibling tools) and the absence of annotations and output schema, the description is insufficiently complete. It does not mention return values, prerequisites, or how this tool fits into a workflow. More context is needed for an agent to use it effectively.

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?

The input schema has one optional parameter with no description (0% coverage). The description adds only a default value ('Default: firefox-default'), but does not explain the parameter's meaning, valid values, or how to choose a preset. The agent lacks sufficient semantic information to use the parameter correctly.

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 ('Apply a stealth preset') and the method ('via BiDi preload'), providing a specific verb and resource. It also gives a default preset, which adds context. However, it does not explicitly distinguish itself from similar sibling tools like inject_stealth_hook or inject_stealth_to_workers, leaving some ambiguity.

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 guidance is provided on when to use this tool versus alternatives. Among many stealth-related sibling tools (e.g., inject_stealth_hook, list_stealth_presets), there is no explanation of the appropriate context or prerequisites. The description only mentions a default preset but lacks usage recommendations.

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