Get Course Assignments

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

The description discloses that by default it fetches each assignment detail/upload page, which is a behavioral trait. It also hints at performance implications. No annotations are provided, so the description carries the full burden; it does not discuss auth needs, rate limits, or other side effects, but covers the key default behavior.

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 extremely concise with two short sentences. It front-loads the main purpose and adds a useful usage hint without any wasted words. Every sentence earns its place.

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?

Despite the presence of an output schema, the description fails to explain key parameters like limit and compact, which are critical for proper usage. Given the tool has 4 parameters and siblings offer similar functionality, the description is insufficiently 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 0%. The description only explains the include_details parameter and its effect. The required 'course' parameter is implied but not defined, and 'limit' and 'compact' are left entirely undocumented, leaving the agent to guess their meaning.

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 that the tool returns a course's assignment list, specifying the resource and action. It also mentions the default behavior of fetching details, but does not explicitly differentiate from sibling tools like get_dashboard_assignments.

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 provides guidance on when to set include_details=false for a faster read, which implies when to use the default vs. the opt-out. However, it does not compare this tool to alternatives or state when not to use it.

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