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

Beyond the annotations, the description discloses important behavior: collection is sequential rather than atomic, console events may predate it, output is bounded and redacted (no cookies, headers, bodies, query values, other sites' paths), unproved console contexts are withheld, website messages are untrusted, and it requires read/diagnostics_read permissions.

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 front-loaded with the purpose and is dense with useful operational detail. It is somewhat long for a two-parameter tool, but most sentences earn their place; only the final 'Read-only' mildly repeats the annotation.

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?

No output schema exists, so the description should clarify return values. It hints that 'the next task_state returns interaction.snapshot.rich and an image only when coherent' but does not directly describe what task_diagnostics itself returns, leaving the response shape ambiguous despite otherwise rich behavioral context.

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 carry parameter meaning. It lists the kind categories (console, network, assets, bundle) and explains what the bundle collects, but it does not fully define each enum value's distinct output or add meaning for task_id.

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 states a clear verb and resource: 'Read console, network or public asset metadata from the task-owned tab.' It distinguishes the diagnostic kinds and mentions the relationship to task_state, but it does not explicitly differentiate this tool from siblings like task_observe or browser_run.

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?

It provides a prerequisite ('Needs read and diagnostics_read') and implies the tool's role, but it never explicitly states when to use it versus alternatives such as task_observe or task_state. Usage is inferable rather than spelled out.

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