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

Annotations already establish read-only/idempotent behavior; the description adds non-obvious details: formatting is stripped while paragraph/list structure is kept, uploaded Skool videos and attached files are omitted, and only accessible lessons are returned. This materially improves invocation expectations without contradicting annotations.

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 short sentences with no repetition; scope and return shape are front-loaded before caveats. Every sentence contributes to correct selection or interpretation.

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?

Because there is no output schema, the description carries return-value burden and does so: it describes text, video link, uploaded_video flag, omitted files, and access scope. For a three-ID read operation, that is enough to call and interpret it correctly.

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?

All three parameters have complete schema descriptions pointing to group, course_id, and lesson_id sources, so the schema already does the work. The description does not add syntax or constraints for these inputs beyond what the schema provides.

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 a specific resource (one Classroom lesson) and states exactly what it returns: text and linked video. It is clearly a read-one operation, though it does not explicitly contrast with get_course or list_courses.

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?

There is no explicit when-to-use guidance or alternative routing; the only usage-related constraint is that it returns only lessons the account can open. An agent can infer it is for fetching a single known lesson_id, but the description does not say when to choose it over get_course or list_courses.

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