interceptor_camoufox_info

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

No annotations are provided, so the description handles behavioral disclosure. It indicates a read-only operation (Get) and specifies the output (wsUrl and snippets), which is transparent enough for an info retrieval tool. However, it could mention that the target must be active.

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 a single sentence with only 16 words, front-loaded with the verb 'Get', and contains no extraneous information. Every word earns its place.

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 simplicity (1 required parameter, no output schema), the description adequately explains what the tool returns (wsUrl and snippets) and implies the precondition (target launched). Output specifics are sufficiently documented.

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 100% with the target_id parameter already described as 'Target ID from interceptor_camoufox_launch'. The description adds little beyond this, so baseline score of 3 applies.

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 it retrieves wsUrl and Playwright snippets for a camoufox target, using a specific verb and resource. It distinguishes itself from sibling tools like launch and list by focusing on info retrieval for an existing target.

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 implies usage after launching a target via interceptor_camoufox_launch, but does not explicitly state when to use this tool vs alternatives like list (which may also provide info) or provide any exclusions or prerequisites beyond the required target_id.

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