list_sessions

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful scope context that only explicitly connected tabs are returned, but says nothing about the return shape, ordering, or why a mutating-sounding parameter like expectedRevision would exist on a read-only listing.

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?

Two short sentences with the core purpose front-loaded and no filler. It is efficiently written, though the second sentence is arguably parameter advice rather than core purpose.

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 no output schema and three undocumented parameters, an agent cannot tell what the response contains or what role requestId and expectedRevision play. For a listing tool this is a meaningful gap even though the read-only annotations lower the safety burden.

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 carries the full burden, but it only mentions sessionId and only as a disambiguation hint, not as an explanation of the field. requestId and expectedRevision are left completely undefined, and expectedRevision is especially confusing on a read-only list operation.

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?

States a specific verb and resource (list / connected editor tabs) and adds a scope qualifier, 'explicitly connected,' so an agent knows this is not a session history query. It does not explicitly name a sibling to distinguish itself from list_projects or list_timelines, which keeps it at 4.

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 second sentence gives conditional guidance, but only about choosing a sessionId value when multiple tabs exist, not about when to call this tool versus any alternative. Usage is implied by the name and the word 'List,' with no explicit exclusions.

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