get_syllabus

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

The readOnlyHint annotation already establishes safety, and the description adds useful behavioral context by emphasizing 'untruncated' and the completeness of the content. It does not contradict the annotation and conveys that this tool returns more than a preview, which is valuable beyond the annotation.

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 two sentences, front-loaded with the primary purpose, and immediately provides the key differentiator. Every sentence earns its place with no filler or redundancy.

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 the output schema exists and the tool is a straightforward read-only retrieval, the description fully covers what the agent needs: what it does, when to use it, and why it matters. It also anticipates the likely confusion with the sibling preview tool, making it contextually complete.

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%, and the description does not add additional parameter-level meaning beyond what the schema already provides. The baseline of 3 applies because the schema handles parameter documentation; the description focuses on tool purpose rather than parameter details.

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 states a specific verb + resource: 'Get the complete Canvas Syllabus tab content for a course, untruncated.' It also distinguishes itself from the sibling get_course_content_overview by explicitly contrasting the full syllabus body against a ~1000-char preview, which makes the purpose unmistakable.

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 names get_course_content_overview as an alternative and explains when to use this tool instead: when you need the full syllabus body so that later sections like grading policies and final-exam details remain accessible. This gives clear situational guidance.

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