get_assignments

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

With no annotations, the description carries the full burden. It reveals that the tool returns 'assignments' and 'count', and shows the fields in the return format. However, it omits details like pagination, ordering, whether it returns only published assignments, or required permissions. The behavioral info is adequate but not comprehensive.

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 concise, using a docstring format with 'Args' and 'Returns' sections. It front-loads the main purpose. Every sentence contributes useful information, though the formatting labels are slightly redundant.

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 a simple tool with one parameter and no output schema, the description covers the basic purpose and return structure. However, it lacks details on pagination, filtering, or permissions. Compared to siblings with similar tool patterns, it is not fully complete but covers the essentials.

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?

The schema only has a type and title for 'course_id' (integer), and schema coverage is 0%. The description adds meaning by specifying it is a 'Canvas course ID' and that it is required, which is useful context beyond the schema.

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 'Get all assignments for a course' with a specific verb and resource. It also mentions the 'course_id' argument, making the tool's purpose unambiguous. It distinguishes from siblings like 'get_assignment' (singular) and other resource-specific get tools.

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?

No guidance is provided on when to use this tool vs. alternatives. There are many sibling tools for different resources (e.g., get_course, get_announcements), but no explicit context or exclusions are given. The description only states what it does, not when or 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.