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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful ordering behavior ('newest edit first'), but does not mention pagination behavior or result limits beyond what is implicit in the schema.

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?

The description is a single well-structured sentence with no wasted words. The core operation and ordering are front-loaded, and the optional filter is clearly appended.

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 simple list tool with rich annotations but no output schema, the description covers the core purpose and ordering. However, it omits pagination semantics and does not describe the shape or contents of the returned lecture list, leaving gaps an agent must infer from the schema.

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%, so the description carries the burden of explaining all three parameters. It adds meaning for the title filter (likely the 'query' parameter) but says nothing about 'skip' or 'limit', including the default limit of 20 and maximum of 50 documented only in the 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 uses a specific verb ('List') and resource ('the user's recorded lectures'), and adds meaningful scope: newest edit first and optional title filtering. It is distinguishable from get_lecture, which retrieves a single lecture, though it does not explicitly name siblings like search_library or list_lecture_shares.

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 phrase 'optionally filtered by title' implies a filtering use case but gives no explicit guidance on when to use this tool versus alternatives such as search_library or list_lecture_shares. There are no stated exclusions, prerequisites, or sibling-routing instructions.

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