Get Course Outline

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

No annotations exist, so the description carries the disclosure burden. It conveys read-only behavior ('Fetch... return its full text'), the content structure ('week-by-week schedule'), and a fallback behavior when no outline link exists. It does not mention permissions or error conditions, but for a fetch tool the essential behavior is covered.

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 bit lengthy but front-loaded with the core purpose. The examples and workflow instructions earn their place; however, the block of quoted questions could be condensed without losing meaning. Overall, it is concise enough for the value it provides.

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 only one parameter and an output schema present, the description need not detail return values. It thoroughly covers when to use, how to chain with sibling tools, and a fallback case, making it fully complete for its intended 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?

Schema description coverage is 100%, with courseId already described as 'The course org unit (ou) ID from list_courses, e.g. 123456'. The description adds no extra parameter context beyond the schema, so a baseline of 3 is appropriate.

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 it 'Fetch the official syllabus and return its full text,' using a specific verb and resource. It also distinguishes itself from siblings by framing its role in chronological orientation and referencing get_content and get_topic_file as follow-ups.

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 explicitly lists when to use the tool ('Use to answer...', 'WHENEVER user asks about content with chronological language') and provides alternatives ('If no outline link exists, check get_content'). It also instructs to call get_content & get_topic_file afterward, making the intended workflow very clear.

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