get_recent_sessions

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description does not need to restate those. It adds meaningful behavioral context by explaining ownership-based visibility: non-owners see only their own sessions while the owner token sees all, plus the output format in the sample.

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 compact and front-loaded: a one-line summary, a usage-direction sentence, and a parameter note. Every sentence serves a distinct purpose with no filler or repetition.

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 low-complexity tool with one optional parameter. The description covers what it returns, how results are ordered, the visibility rules, and how it relates to sibling tools. There is no output schema, but the sample shape compensates adequately.

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 0%, so the description carries full responsibility for explaining the 'limit' parameter. It does so clearly: 'max rows to return (default 10), newest first.' This adds semantic meaning beyond the raw integer schema and fully compensates for the missing schema description.

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 opens with a specific verb and resource: 'List recent sessions, newest first' and includes a sample result shape. It also distinguishes this tool's role as the discovery entry point for session_ids used by the other get_* tools, making it easy for an agent to know exactly what it does.

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 phrase 'Call this first to discover session_ids for the other get_* tools' gives explicit sequencing and intent, which is strong usage guidance. It does not spell out exclusion cases, but the context makes it clear this is the intended first step before sibling get_* tools.

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