Get Syllabus

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

Adds meaningful context beyond annotations: the content is HTML-converted to plain text and is fenced as untrusted, which is a real behavioral/safety trait for an agent consuming it. Annotations already cover read-only/idempotent/non-destructive, so the description doesn't need to repeat those, and it doesn't. It stops short of saying what happens when no syllabus exists, which keeps it below a 5.

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, no filler. Leads with the core action, then the untrusted-fencing caveat, then the fallback routing — a sensible front-loaded ordering.

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?

No output schema exists, and the description covers the return shape ('plain text, converted from Canvas HTML') and its trust framing, plus fallbacks. The only gap is not stating the outcome when a course has no syllabus, which is minor for a simple single-param read tool.

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?

Only one parameter and schema coverage is 100%, with the schema itself explaining course_id format and pointing at list_courses. The description adds no parameter-specific meaning, which is acceptable at baseline 3 when the schema does the work.

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 and resource ('Get a course syllabus as plain text') plus the transformation applied ('converted from Canvas HTML'). It also implicitly distinguishes itself from syllabus_digest and list_course_files by naming them as different routes, so an agent can pick it apart from siblings without opening a 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?

Explicitly routes the agent: if the instructor uploaded the syllabus as a file, go to list_course_files instead, and syllabus_digest is named for date/weight extraction. Both the alternative and the condition that selects it are stated.

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