session_record_list

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

With no annotations, the description alone must disclose behavior. It implies a read-only operation by using 'List', but does not explicitly state there are no side effects, nor does it describe any constraints (e.g., scope of 'all' sessions). It provides basic but minimal behavioral context, adequate for a simple zero-parameter tool.

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 a single concise sentence that front-loads the action and resource. There is no wasted text, and it is easily scannable.

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 zero-parameter, no-output-schema tool, the description is reasonably complete. It specifies what is listed and the information returned. However, it lacks any mention of scope (e.g., all sessions for the current workspace or user) or ordering, leaving a minor ambiguity. Still, given the simplicity, it is adequate.

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 and the schema is fully documented by being empty. The description adds no parameter-specific information because there are none to describe. Per the baseline for 0-parameter tools, this is sufficient.

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 clearly states a specific verb ('List') and resource ('recording sessions') along with the attribute ('their status'). It distinguishes from sibling tools like session_record_start/stop/events/replay, which are action-oriented, so an agent can easily tell this is the listing operation.

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 provided on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparisons with sibling tools like session_record_events or session_record_replay. The agent must infer from the name and description when to call this.

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