list_sessions

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does disclose the read-only listing nature, the 'all sessions' scope, and the included field types. It does not mention ordering, pagination, or potential performance impact, though the optional limit parameter in the schema partially covers constraints.

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 front-loaded sentence that efficiently communicates the action, resource scope, and return fields. There is no filler or redundancy, and every word adds value.

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 listing tool with one optional, schema-documented parameter and no output schema, the description gives enough context to invoke it correctly: it names the resource, the scope, and the returned content. Minor details like ordering or multi-workspace behavior are absent but not critical for this tool.

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 only parameter, limit, is already fully documented in the schema as 'Maximum number of sessions to return', giving 100% schema description coverage. The tool description adds no additional parameter semantics, but the schema already provides the necessary meaning.

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 specific action ('List'), a specific resource ('all recorded browser forensic debugging sessions'), and the content returned ('metadata, timestamps, and stats'). This clearly distinguishes it from singular tools like get_session and from mutation tools like delete_session.

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 implies that this tool is for retrieving all sessions, which an agent can infer from the word 'all' and the sibling tool context. However, it never explicitly states when to use this tool versus alternatives such as get_session or export_session, nor does it list exclusions.

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