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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value beyond them: the required OAuth scope and the non-obvious filtering rule that "a track is listed only once media reached it," which explains why a declared track may be absent from results.

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 tight sentences, front-loaded with what the manifest is, followed by the filtering caveat and the auth requirement. 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 describe the payload shape (participants, tracks, time bounds) plus the auth requirement. It lacks error/not-found behavior and any hint about the session_id's provenance, but is otherwise sufficient for a one-parameter read.

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 0% and the single session_id parameter is never explained — no format, source, or lookup guidance. The manifest framing implies the id selects the session, but the description does nothing to compensate for the empty schema.

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 names the resource precisely ("the raw session manifest") and enumerates its contents — participants, tracks with recorded media, time bounds — so an agent knows what it retrieves. It does not explicitly contrast itself with siblings like verify_session or run_media_check, so it stops short of a 5.

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 only usage-relevant statement is the prerequisite "Requires scope mcp:read." There is no guidance on when to call this versus verify_session, run_media_check, or list_sessions, and no exclusions or conditions given.

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