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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description goes beyond them by disclosing the exact shape of each returned entry (channel, kind, method, payload, outcome, duration, t_ms) and explaining that t_ms encodes inter-action gaps — real behavioral context, though nothing about ordering guarantees or error behavior for a bad id.

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 return shape, then filtering. The t_ms aside earns its place because it explains why the field matters, and there is no 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?

With no output schema, the description carries the return-value burden and does so well, enumerating every entry field and the semantics of t_ms. It is only slightly short of complete: it does not say what happens on an unknown id or how entries are bounded/ordered beyond 'in order'.

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% and all five parameters are documented there, so the baseline is 3. The description's 'page through with limit/offset; narrow with channel or kind' only restates the schema and adds no format or edge-case detail beyond it.

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?

States a specific verb and resource ('Read a stored recording's entries in order') and immediately characterizes the unit being read, so it is distinguishable from the sibling ios_actions_recordings (which lists recordings) and the record_start/status/stop lifecycle tools.

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 closing clause gives operational guidance on paging ('limit/offset') and narrowing ('channel or kind'), but there is no explicit when-to-use/when-not framing and no mention of which sibling produces the required id — that only appears in the schema description.

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