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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds scope ('their own list') and domain boundaries, but says nothing about result size, ordering, or what an empty list means.

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?

Three short sentences, front-loaded with the positive trigger followed by the exclusions. Nothing is redundant or padded; every clause aids routing.

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 read-only, closed-world tool with one optional, fully documented parameter and no output schema, the definition covers what an agent needs to select it. Minor gaps remain around what the returned list contains, but those are not blocking.

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?

There is a single optional parameter, 'tap', and schema coverage is 100% with a description explaining it is the token from keep_progress. The tool description adds no further meaning about this parameter, so the schema carries the burden and baseline 3 applies.

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 frames the tool as returning the user's own saved sessions, favourites, or personal list, which is a recognizable resource scope. It implicitly separates this from the broader browse_library/find_sessions siblings by emphasizing 'their own list,' though it never states a verb like 'list' or 'retrieve' outright.

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?

It gives a clear when-to-use trigger ('asks for the sessions they saved, their favourites or their own list') plus explicit exclusions for medical questions, emergencies, crises, and general meditation chat. What it lacks is a named alternative sibling to redirect to, so the routing is stated by topic rather than by tool.

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