Get Assignments

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

Annotations already set readOnlyHint=true, and the description reinforces a no-mutation read operation. It adds useful behavioral detail about returned data (dropbox submissions, quizzes with due dates, status, rubric info) and the optionality of course scope. It doesn't describe pagination or ordering, but that is minor for a simple read-only lookup.

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?

Two sentences, front-loaded with the operation and scope, followed by a concrete use trigger. No redundancy with the title or schema.

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 one-parameter read-only tool with high schema coverage, the description sufficiently explains what it returns and when to invoke it. It could be strengthened by explicitly contrasting with get_upcoming_due_dates, which also involves due dates, but the stated trigger conditions mostly cover the disambiguation.

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%, and the schema already explains that courseId is optional and means 'Course ID to get assignments for' and that omission returns assignments for all enrolled courses. The description corroborates this ('specific course or all enrolled courses') but does not add new semantics beyond the schema; 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?

Description states a specific verb ('Fetch') and resource ('assignments and quizzes'), defines the scope ('specific course or all enrolled courses'), and lists concrete included data (dropbox submissions, quizzes with due dates/status/rubric info). This allows an agent to distinguish it from siblings like get_course_content or get_my_grades.

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?

Explicit trigger phrase 'Use this when...' enumerates user intents: assignments, homework, what to submit, quizzes, or assignment details and rubrics. It does not state when NOT to use it or name alternatives such as get_upcoming_due_dates for due-date-only queries, so it misses explicit exclusion guidance.

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