get_course_contents

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

No annotations exist, so the description carries full burden. It discloses the token requirement for file URLs and mentions `download_file`, but does not discuss auth needs, rate limits, or side effects. This is adequate but not exhaustive.

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 concise with exactly three sentences plus an Args list. It is front-loaded with the main purpose and avoids redundancy or 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?

Given a single required parameter and an output schema, the description fully explains the parameter and a key behavioral detail about file URLs. The agent has sufficient information to use the tool 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?

Schema provides only type and title for `course_id` (0% description coverage). The description adds meaningful semantics: 'numeric course id (see list_my_courses)', which guides the agent on how to obtain the value.

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 explicitly states it returns sections, modules, and file URLs for a course, using a specific verb and resource. It differentiates from sibling `download_file` by mentioning the token requirement and suggesting that tool.

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?

It provides clear usage context: file URLs need token appended, references `list_my_courses` for course IDs, and suggests `download_file` as an alternative. However, it does not explicitly exclude other cases or compare with other siblings like `search_courses`.

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