browser_start_tracing

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

No annotations provided, so description must fully disclose behavioral traits. It fails to mention key details: whether starting a new trace stops any existing trace, impact on browser performance, authentication requirements, or any side effects.

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?

Single sentence, no filler. Direct and to the point. Every word adds value.

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 large set of sibling browser tools and the presence of an output schema, the description should provide more context about when to use this tool, how it relates to 'browser_stop_tracing', and what the output contains. It currently lacks this completeness.

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%, and the only parameter (session_id) is not explained in the description. The description adds no semantic value beyond what the schema provides (optional, nullable). The parameter's purpose remains ambiguous.

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?

Description clearly states the action ('Start') and the resource ('Playwright trace'), and explains what it captures ('screenshots + DOM snapshots') for later inspection. It implicitly distinguishes from the sibling tool 'browser_stop_tracing' by focusing on starting rather than stopping.

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 versus alternatives (e.g., when to start tracing vs. using screenshots or snapshots directly). There's no mention of preconditions, such as needing an active session, or 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.