list_me_sessions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond repeating the endpoint—no mention of return format, pagination, or what data is included. Since it adds nothing beyond annotations, the score is low.

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 extremely short, but it contains redundancy: 'Get me sessions' and 'GET /api/me/sessions' convey the same information. It's not front-loaded with any distinguishing context. While brevity is good, it sacrifices necessary clarity, so it's average.

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?

This is a simple no-param tool with an output schema, but the description is incomplete for an agent to understand what it returns or when to use it. Given the large sibling set, it needs to specify that it lists the current user's sessions and how that differs from list_sessions. The lack of any context makes it inadequate.

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 has zero parameters, so per the rubric the baseline is 4. The description doesn't need to explain parameters, and it doesn't mislead. It correctly implies a simple call with no input.

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 'Get me sessions' and the endpoint, which identifies the verb and resource, but it is vague. It doesn't clarify what 'sessions' refers to (listening sessions, auth sessions, etc.) and doesn't differentiate from many sibling list tools like list_sessions, list_sessions_open, or list_me_listening_sessions. It is barely more than a tautology, though the endpoint adds a slight hint.

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?

There is no guidance on when to use this tool versus alternatives. No context, no exclusions, no mention of which sibling to choose under what circumstances. The description provides zero usage direction.

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