list_replays

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

With no annotations, the description carries the full burden and discloses almost nothing: no pagination behavior (page/pageSize exist), no default range, no ordering, no volume/limit caveats. Only the word "List" hints at a read-only operation, which is insufficient for an 8-parameter listing 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 sentence is tight and front-loaded with no filler, but for a tool with 8 parameters, 3 required and a nested filters object, a single clause is under-specified rather than appropriately sized.

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?

No annotations, no output schema, 13% schema coverage, 8 parameters including a nested free-form filters object, and several near-identical sibling tools. An agent has almost nothing to determine correct invocation or expected return shape.

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 13% across 8 parameters, and the description adds nothing about startAt/endAt (integers — epoch ms? seconds?), search semantics, minDuration units, or the shape of the nested filters object. The single phrase "for a website" only weakly points at websiteId.

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?

"List session replays for a website" gives a clear verb and resource, but the sibling set contains list_session_replays, list_saved_replays, and get_replay, and the description does nothing to distinguish this tool from any of them. An agent cannot tell which replay-listing tool to pick without opening schemas.

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?

There is no guidance on when to use this versus list_session_replays, list_saved_replays, or get_replay, and no stated prerequisites (e.g. that a websiteId is required). Usage must be inferred entirely from the name.

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