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

With no annotations provided, the description carries full responsibility. It discloses entry fields, the meaning of t_ms for time gaps, and ordering. However, it does not specify the default sort beyond 'in order', the exact return shape, or error behavior, making it adequate but skeletal.

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?

Three sentences, front-loaded with the core action, then field content, then pagination/filtering guidance. Every sentence earns its place with zero filler.

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 5-parameter read tool with no output schema, the prose covers the result format (fields per entry), pagination, and filtering. It omits edge cases like invalid ids or empty recordings, but id provenance is covered in the schema, so the description is largely complete.

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 100%, so the baseline is 3. The description reinforces limit/offset and channel/kind usage, but adds no schema-independent meaning beyond that reinforcement.

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 ('Read') and resource ('stored recording's entries'), and clarifies ordering behavior ('in order'). It clearly separates this from the recording/stopping/replay siblings through the resource focus, though it does not explicitly name an alternative.

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?

It gives explicit directions for pagination and filtering: 'Page through with limit/offset; narrow with channel or kind.' This tells the agent exactly how to constrain results. It stops short of naming a sibling alternative for when this tool should not be used, so not a 5.

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