List Sessions

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing behavioral beyond that – no mention of scope, filtering, pagination, or what a "session" contains – so it contributes no value on top of the structured metadata.

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?

It is short and front-loaded with the verb and resource, but the second sentence ("Operation lifecycle and session management") is filler that adds ambiguity rather than information, so not every sentence earns its place.

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?

An output schema exists and annotations are rich, so return values and safety needn't be explained. However, the description never clarifies what a "session" is in this system or how listing differs from the operation lifecycle tools, leaving a real gap for an agent deciding whether to call it.

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 coverage is 100%, so all four parameters are documented in the schema, which sets the baseline at 3. The description adds no parameter meaning (e.g., which params actually apply to a list operation versus start/get_progress), so it neither helps nor compensates.

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?

"List sessions (tm_operations)" gives a clear verb and resource, but the follow-up "Operation lifecycle and session management" is vague and actually describes the operation family rather than this tool, leaving it poorly distinguished from siblings like tm_operation_get_progress or tm_operation_start.

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?

No indication of when to list sessions versus using the other tm_operation_* tools, and no prerequisites or context for choosing this tool over sibling alternatives are provided.

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