camofox_download_trace

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

With no annotations, the description must fully disclose behavior. It says 'streams a zip' but doesn't detail whether the download returns a file or URL, if authentication is needed, or any side effects. The mention of trace.playwright.dev provides context but not behavioral specifics.

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?

Extremely concise: two sentences, no filler. The first sentence states the purpose, the second adds context about the output format. 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?

Without an output schema or annotations, the tool is underspecified. It doesn't explain the response format (binary stream, URL, etc.), error scenarios, or that the trace file must be obtained via list_traces. For a tool with two required params, this is insufficient.

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 descriptive parameter names and descriptions ('Session owner identifier', 'Trace zip filename'). The description adds no additional meaning beyond 'trace file' and 'trace zip', so baseline 3 is appropriate.

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 'Download a trace file' and specifies 'Streams a Playwright trace zip for viewing in trace.playwright.dev.' This distinguishes it from sibling tools like camofox_list_traces (listing) and camofox_delete_trace (deletion).

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 on when to use this tool vs alternatives. It doesn't explain prerequisites (e.g., trace must exist) or that it's for downloading a specific trace by filename. No mention of when not to use it.

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