Get Course Syllabus

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

Annotations already cover read-only and open-world behavior, but the description adds real value beyond them: the dual read/download behavior triggered by downloadPath, the markdown return format, and the required user-consent step before writing a file. It does not describe failure modes for an invalid courseId or a bad download path.

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 sentences, front-loaded with the primary action and return value, with the conditional download behavior and the user-consent warning ordered by importance. There is minor overlap between the opening 'optional attachment' phrasing and the later downloadPath sentence, but nothing wasteful enough to penalize heavily.

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 no output schema, the description correctly states what is returned (overview as markdown) and explains the file-download branch and the user-consent prerequisite. Combined with a fully documented 2-param schema and safety annotations, an agent has what it needs, though error/edge-case behavior is unaddressed.

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 coverage is 100%, so both parameters are already documented. The description restates that downloadPath triggers an attachment download, which adds mild behavioral framing but no format or syntax detail beyond the schema's 'absolute path to the directory' description. Baseline 3 applies.

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?

States a specific verb ('Fetch') and resource ('syllabus/overview text and optional attachment for a course'), and clarifies the return format (markdown overview). This cleanly separates it from siblings like get_announcements, get_assignments, or get_course_content without needing to open any schema.

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?

Gives clear conditional guidance: pass downloadPath only when the attachment should also be downloaded, plus a mandatory pre-call step (ask the user where to save). It does not name an alternative for retrieving files (e.g. the sibling download_file), so there is no explicit when-not guidance.

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