cdp_list_sessions

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

With no annotations, the description carries the burden of disclosing behavior. It clarifies the scope ('all active CDP sessions in this MCP process') but does not mention whether the operation is read-only, what the return format is, or any side effects. The verb 'list' implies a safe read, but richer context would improve transparency.

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 sentence that is front-loaded and contains only essential information. Every word earns its place, with no redundant phrasing.

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?

For a simple, parameterless list tool, the description provides adequate context about what is listed and the scope. It doesn't describe the return value, but no output schema exists and the operation is straightforward. Sibling tools and the name reinforce its purpose.

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?

The tool takes zero parameters, so the schema is complete (100% description coverage). The description adds no parameter details, but with no parameters there is nothing to explain; the baseline for 0 params is 4.

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 action ('List') and the resource ('all active CDP sessions') with a specific scope ('in this MCP process'). This distinguishes it from sibling tools which perform actions on sessions (e.g., connect, navigate) rather than listing them.

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 purpose is implied: it is used to see which CDP sessions are currently active. However, there is no explicit guidance on when to use this tool versus alternatives, such as after connecting or before performing session-specific operations.

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