Get Course Syllabus

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

Annotations declare readOnlyHint=true, and the description is consistent with that. It adds valuable behavioral detail beyond the annotation by disclosing the optional attachment download side effect, the markdown return format, and the mandatory user-consent precondition for downloadPath.

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 and well-structured: purpose, return format, conditional download behavior, and a critical usage warning. Every sentence adds value, and the important user-consent instruction is prominently highlighted without unnecessary padding.

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 two-parameter read operation, the description covers the return format, the optional download behavior, and the key precondition for using downloadPath. Given the low complexity and full schema coverage, no critical information is missing.

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 already fully describes both parameters, giving a baseline of 3. The description adds extra meaning by clarifying that providing downloadPath triggers an attachment download and by requiring user confirmation before calling with that parameter, which goes beyond the raw 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 clearly states the action ('Fetch') and the resource ('syllabus/overview text and optional attachment'), and it clarifies that the overview is returned as markdown. However, it does not explicitly differentiate itself from sibling tools like get_course_content, so the distinction is clear but not directly stated.

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 description gives clear context for when to call the tool and provides an explicit conditional guideline: if downloadPath is provided, the user must first be asked where to save the file. It does not mention alternative tools or when to avoid this tool, but the usage context is reasonably complete.

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