list_session_replays

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read operation but does not disclose pagination behavior despite page/pageSize parameters, does not explain the required date-range constraints, and says nothing about return shape, permissions, or rate limits.

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 single sentence is front-loaded and free of filler, but it is too thin for a 7-parameter tool with four required parameters. Brevity here reflects under-specification rather than efficient communication.

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 7 parameters, no annotations, no output schema, and no parameter descriptions, the definition is materially incomplete. It identifies the core resource but omits date-range semantics, pagination, search behavior, and return expectations that an agent needs to invoke 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% across 7 parameters, and the description only hints at sessionId. It does not explain websiteId, startAt, endAt, page, pageSize, or search, so an agent must infer all parameter meaning from bare names and types.

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 replay recordings') and adds a scoping qualifier ('linked to one session'), which distinguishes it from broader siblings like list_replays and list_saved_replays. It does not explicitly name those alternatives, but the resource and scope are clear.

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 'linked to one session' implies that a sessionId is required, but the description never states when to use this instead of list_replays, list_saved_replays, or get_replay. No exclusions, prerequisites, or alternative-selection guidance are provided.

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