inject_stealth_hook

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

With no annotations, the description carries the full burden. It reveals key behavioral traits: stealth hardening, toString masking, channel-emitting Proxy, timing neutralization, and BiDi preload installation. It does not mention reversibility or permission needs, but the disclosed details are substantial.

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 two tight sentences. The first packs critical technical context; the second provides essential usage guidance. No fluff or redundancy.

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 hook with multiple options), the description covers purpose and boundaries but lacks parameter details and return value information. No output schema, so return expectations are omitted. Adequate but not fully self-contained.

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 0%, so description must explain parameters. It mentions 'dotted global paths' (targetPath) and 'timing neutralisation' (neutraliseTiming/timingMaxGapMs), but does not explain channelName, capture, or the wraps array structure in sufficient detail. Only partial coverage for two of the three key parameters.

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 specifies the tool's action: rendering a stealth-hardened wrap over global paths with specific techniques (Function.toString masking, Proxy). It also distinguishes from sibling inject_stealth_to_workers by stating 'Main world only'. The verb 'render' and resource 'stealth-hardened wrap' are precise.

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 provides explicit guidance: 'Main world only — use inject_stealth_to_workers for worker realms.' This clearly tells the agent when to use this tool versus a named alternative.

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