console_capture_start

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose meaningful traits: the capture is bounded, it runs on a real-browser tab, and it does not foreground the tab. However, it does not explain what 'bounded' means in terms of timeout/max_entries, whether capture starts fresh, or any side effects on the tab.

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?

Two sentences with no filler. The key behavior is front-loaded, and the follow-up tools are named immediately. Every part of the description 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?

The start/read/stop lifecycle is covered, and an output schema exists so return-value details are not strictly required. However, with no annotations and zero parameter documentation, the description leaves the meanings of timeout, session_id, and max_entries underspecified, which is a real gap for correct invocation.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It does not mention timeout, session_id, or max_entries at all. The phrase 'bounded' hints at timeout/max_entries, but no concrete parameter meaning is provided, leaving the agent to rely on parameter names alone.

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 uses a specific verb and resource: 'Start a bounded Runtime console and exception capture on a real-browser tab.' It clearly distinguishes this start action from sibling tools like get_console_messages and console_capture_stop by naming the capture lifecycle phase.

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 gives explicit process guidance: use get_console_messages while running and console_capture_stop when done. It does not explicitly list alternatives or when-not-to-use cases, but the workflow context is clear enough for an agent to understand the tool's place in the lifecycle.

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