List all recordings captured in this session and from the persistent manifest, with file path, duration, size, and timestamp. Use it to locate and review recordings.
List all recordings captured in this session and from the persistent manifest. Includes file path, duration, size, and timestamp for each recording.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of recordings to return. Default: 20. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It conveys that the operation is a listing (implying read-only), covers both current session and persistent manifest, and specifies the output fields. This is more informative than a minimal description, though it does not explicitly state side-effect-freeness or ordering.
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 sentences with no filler. The core purpose and scope are front-loaded, and the field list adds concrete value without redundancy.
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 simple listing tool with one optional parameter and no output schema, the description adequately covers what the tool returns and its data scope. Minor details like ordering or empty-result behavior are absent, but they are not critical for this tool's completeness.
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 only parameter, 'limit', is fully documented in the schema with a default value and meaning. Since schema_description_coverage is 100%, the description does not need to add parameter details, and it doesn't. This meets the baseline for high schema coverage.
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 the specific action ('List all recordings') and resource ('recordings captured in this session and from the persistent manifest'). It also enumerates the included fields (file path, duration, size, timestamp), which distinguishes it from sibling tools like start_recording or get_recording_status.
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 verb 'List' and scope ('all recordings') imply the appropriate use case: enumerating existing recordings rather than starting/stopping or checking status. However, no explicit alternatives or exclusions are mentioned, so the guidance is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.