List Sessions

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

No annotations are provided, so the description carries the full burden. It does disclose one behavioral trait—optional automatic pagination via fetch_all—but omits safety profile, authentication needs, rate limits, and what happens when pagination is not requested. The partial pagination detail earns a 3 rather than a 2.

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 a single sentence with the verb-resource front-loaded, but the phrase 'to retrieve sessions natively' is redundant and slightly awkward, adding length without informational 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 list tool with four undocumented parameters and no annotations, the description is too thin. Although an output schema exists and return values need not be explained, the lack of parameter semantics and behavioral detail leaves the agent without enough context to invoke it confidently.

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% for four parameters (_meta, fetch_all, page_size, page_token). The description vaguely references pagination but does not explain any parameter by name or semantics, so it fails to compensate for the coverage gap.

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 verb and resource ('List sessions'), making it clear apart from get_session or create_session. However, it does not explicitly differentiate from other list-style siblings like list_activities or list_sources, and the trailing phrase about pagination adds no clarifying purpose.

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 guidance is given on when to use this tool versus get_session, list_activities, or any alternative. There are no exclusions or prerequisites; the agent must infer usage entirely from the name.

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