list_sessions

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

Without annotations, the description carries the full behavioral burden. It usefully discloses ordering (newest first) and a default limit, and 'list' implies a read-only operation, but it does not mention permissions, max limits, or whether it returns metadata. The output schema covers return values, so that omission is acceptable.

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 two front-loaded sentences with an args section, no filler, and the key scoping behavior ('newest first') is stated early. 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?

Given the simple one-parameter schema and the presence of an output schema, the description is nearly complete. It could clarify the scope of sessions (e.g., all users or only the caller's), but otherwise an agent has enough to call it correctly.

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% and there is one parameter. The description adds meaning beyond the schema by explaining that limit is the 'max number to return' and states the default (10). This fully compensates for the undocumented schema parameter, though it does not mention minimum or maximum bounds.

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 recent recording sessions'. It is clear what the tool does, but it does not distinguish itself from siblings like get_status or get_transcript, which also relate to recording sessions.

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 description implies usage by saying it lists recent sessions, newest first, but gives no explicit when-to-use guidance or alternatives. An agent can infer it is for viewing past sessions, but there is no routing advice.

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