console_read

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'read', implying a non-destructive operation, but does not mention the 'clear' parameter or its side effects, nor any requirements like attached devtools or return format. This is insufficient for a tool with zero annotation coverage.

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 clear sentence with no redundant words, front-loading the verb and resource. It achieves high conciseness and is easy to parse, with no fluff.

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 description is too sparse to be complete: it lacks parameter explanations, return format, and any preconditions such as requiring devtools to be attached. For a tool with 2 parameters and no output schema, this is inadequate for reliable 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. It only implies tabId via 'for a tab' but does not explain the 'clear' parameter at all, leaving its semantics undocumented. This fails to provide necessary parameter meaning beyond the bare schema.

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 the tool reads console/log entries for a tab, using the verb 'read' with a specific resource. It differentiates from network tools by specifying console/log, though it does not elaborate on entry types or whether it includes errors/warnings, so it is clear but not fully detailed.

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?

There is no guidance on when to use this tool versus alternatives like network_read or network_requests. The description only states what it does, not when to prefer it or prerequisites such as devtools_attach, leaving the agent to infer usage context.

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