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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds genuinely new behavior — newest-first ordering and the returned field set — but says nothing about pagination interaction with `limit`, so the added value is modest.

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?

Two tight sentences with the core listing behavior front-loaded and the filter hint trailing. Every clause carries information; no filler or tautology.

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 a 2-param, all-optional, read-only tool at full schema coverage, the main remaining gap would be return shape — and the description enumerates the returned fields ('id, device, label, when it ran, what it captured'), compensating for the absent output schema. It does not mention session/prerequisite requirements, a minor omission.

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 coverage is 100%, so both `udid` and `limit` are already documented in the schema. The description only restates the `udid` filter ('Filter by device with `udid`') and adds no syntax, format, or semantics beyond what the schema provides, so baseline 3 applies.

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 ('List stored action recordings') plus the sort order and the fields returned, which distinguishes it from the sibling read-one tool ios_actions_recording_read. It never names that sibling explicitly, so the differentiation is implicit rather than stated.

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 description gives filtered usage via `udid`, which tells the agent how to narrow results, but it never states when to use this list tool rather than ios_actions_recording_read or ios_actions_replay. Usage is implied, not spelled out.

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