list_assignments

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

No annotations are present, so the description carries the behavioral disclosure burden. It provides return fields and defines page_size as a cap, but it does not reconcile 'List all assignments' with a page_size limit or mention pagination, ordering, or invalid-course 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 compact and scannable: a purpose sentence followed by Args and Returns sections. There is no fluff or repeated context, and each line carries necessary information.

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 two-parameter list tool with an output schema, the description supplies enough to call it correctly: course scoping and a page-size limit. Minor details such as how course_id is obtained or behavior when page_size exceeds the total could be added, but they are not critical for a tool of this simplicity.

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 input schema has 0% description coverage, so the description must compensate. It usefully defines page_size as the maximum number of assignments, but course_id is only described as 'the ID of the course', which adds little beyond the property name. Thus compensation is partial.

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 opens with a specific verb and resource: 'List all assignments for a specific course.' This clearly distinguishes it from siblings such as list_courses and list_submissions, which operate on different resources.

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 does not name alternatives explicitly, but the phrase 'for a specific course' establishes clear usage context: call this when you have a course_id and need its assignments. It provides enough guidance for straightforward selection among siblings.

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