Read web debug session status

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the description does not need to re-establish safety. It adds useful context about 'active' sessions and 'summary' output, but does not disclose behavior around missing sessions, pagination, or session lifecycle. That is acceptable but not especially rich.

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?

A single sentence covers both modes with no filler or repetition of predictable details. All words add information.

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?

With one optional parameter, a read-only annotation profile, and an output schema present, this description is nearly complete for a status/list tool. It covers both invocation modes and the active-session scope; only minor details such as sentinel UUID semantics or behavior for unknown session IDs are left to the schema.

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 bears the responsibility of explaining the parameter semantics. It does convey the crucial rule: the optional sessionId switches between listing all active sessions and reading a single session summary. The schema itself provides format and pattern validation, so the description adds meaning beyond the field name.

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 names the exact resource ('web debug sessions') and the two supported operations: listing active sessions or reading one session summary. This makes it easily distinguishable from sibling tools like web_session_start, web_session_close, and web_browser_action.

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 clearly telegraphs the two invocation modes: omit sessionId to list active sessions, provide sessionId to read one summary. It does not explicitly name alternatives or when-not conditions, but the usage context is unambiguous for a read-only status tool.

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