list_recent_sessions

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

No annotations are provided, so the description carries the behavioral burden. It implies a read-only list and discloses the returned content shape (IDs, timestamps, durations, watch URLs), but says nothing about ordering, pagination, or that it reads from a local sessions file.

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?

A single front-loaded sentence with no waste; since there is no output schema, naming the returned fields is the most valuable content it could carry in that space.

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 usefully enumerates the return fields and covers the resource well. It falls short only on default ordering and any routing versus get_latest_session, which are minor gaps for a simple list tool.

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 both parameters (limit, session_file) are already documented in the schema. The description adds no syntax or behavior beyond what the schema provides, matching the baseline for fully-covered schemas.

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 recent QuickCast screen recording sessions') and enumerates returned fields, so the agent knows what it gets. However, it does not distinguish itself from the close sibling get_latest_session, leaving the scope difference (recent list vs. single latest) to inference.

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?

No when-to-use guidance, no mention of the obvious alternative get_latest_session, and no note about when the session_file override matters. The agent is left to guess selection criteria among siblings.

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