cloak_launch

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

The description uses the adjective 'stealth' but does not elaborate on what behavioral traits that entails (e.g., anti-detection measures, session isolation). Without annotations, the description carries full burden, yet it omits critical details like whether this is a read-only or destructive operation, resource cleanup, or state persistence. It is minimally acceptable but lacks depth.

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 extremely concise—just two short sentences—and front-loads the core action. Every word is necessary; no redundant or filler content. Excellent structure for quick comprehension.

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 is a launch operation with 0 required parameters, high schema coverage, and no output schema, the description is minimally complete. It does not explain return values, error conditions, or what happens upon multiple invocations. The low complexity reduces the need for more, but the lack of any return or side-effect description is a gap.

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?

All 9 parameters are fully described in the input schema (100% coverage), so the schema already communicates their meaning. The description adds no additional semantic detail beyond what is in the schema, meeting the baseline expectation.

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 tool launches a 'stealth CloakBrowser instance' using specific verb 'launch' and resource 'stealth CloakBrowser instance'. It distinguishes from sibling tools by noting this must be called before any other cloak tool, making its role as the initial setup action unambiguous.

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?

Explicitly instructs 'Call this before any other cloak tool', providing precise when-to-use guidance. This precludes using other tools without first invoking this one, establishing a clear ordering constraint.

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