List Course Videos

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

With no annotations provided, the description must disclose behavioral traits. It only says 'List', implying read-only, but it does not state safety, authentication requirements, pagination, or what data is returned. The absence of an output schema amplifies the gap—the agent has no idea what the response contains.

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 sentence that directly states the tool's purpose with no redundancy. The action and resource are front-loaded, making it immediately scannable.

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?

The tool is simple with one well-documented parameter, but the description provides no information about the return value or behavioral nuances. Since there is no output schema and no annotations, the description should describe what the list contains (e.g., video metadata, URLs), but it doesn't. This leaves the agent without crucial invocation context.

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?

The schema fully describes course_id as 'Canvas course ID' with 100% coverage, so the baseline is 3. The description references the course implicitly ('for one Canvas course') but adds no extra semantic detail beyond what the schema already 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 clearly states the action ('List') and the resource ('SJTU classroom videos') scoped to one Canvas course. This unambiguously differentiates it from sibling tools like list_course_files or list_course_modules, which target different resource types.

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 guidance is provided about when to use this tool versus alternatives. It does not mention that video_status or get_video_info might be more appropriate for individual video details, nor does it exclude other list operations. Usage context is only implied by the resource name, not explicit.

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