console_start

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Start recording' implies a stateful side effect, but the description does not explain what happens after recording starts, whether it can be called again, or how the recording relates to other console tools.

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, direct sentence with no wasted words, and the key action is front-loaded. It is efficiently structured, though it could include one more sentence of lifecycle context without becoming verbose.

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 tool is simple with one well-documented parameter, but there are no annotations and no output schema. The description is adequate for selecting and starting the tool, but it leaves the recording lifecycle—retrieval and stopping—implicit, which sibling names only partially clarify.

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 100% for the single parameter 'targetId', so the schema already documents its meaning. The phrase 'for a tab' adds minimal context, but it does not provide any additional semantics beyond what the schema states.

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 clear verb ('Start') and names the resource ('recording console logs') with a scope ('for a tab'). It is easily distinguishable from siblings like console_stop and network_start_recording, though it does not explicitly call out the differentiating sibling.

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 no guidance on when to use this tool versus alternatives. It does not mention that console_start should precede console_get_logs, or that console_stop ends the recording, leaving the usage context to inference.

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