browser_trace_start

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

No annotations provided. Description mentions recording performance data but does not disclose behavioral traits such as whether the trace is destructive, what kind of data is collected, or if it requires a page to be loaded. Lacks details on side effects or state changes.

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, concise and to the point. No verbose or redundant information. However, it could be slightly more informative without losing conciseness.

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?

Despite no parameters and no output schema, the description omits important context such as what the return value is (e.g., trace ID), how to stop the trace, or how the recorded data can be accessed. For a session-starting tool, 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?

No parameters exist, schema description coverage is 100%. The description implicitly indicates no parameters are needed. Baseline for 0 parameters is 4; description adds no unnecessary information.

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 tool starts a browser trace session and records performance data. It uses specific verb+resource. However, it does not explicitly differentiate from similar tools like browser_performance_trace or browser_trace_stop, but the name and context imply the distinction.

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 like browser_performance_trace or browser_trace_stop. Does not specify prerequisites or conditions for starting a trace. Agent must infer usage from name alone.

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