blackboard_list_assignments

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

With no annotations, the description carries full burden. It discloses the content returned (due dates, scores, submission status) but omits details like return format, pagination, ordering, or any required permissions. Since 'List' implies a read-only operation, it isn't misleading, but it lacks deeper behavioral context.

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 a single, clear sentence that packs the essential action and scope without waste. Every word contributes to understanding the tool's purpose.

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?

The tool is simple (one parameter, no output schema), but the description does not mention the output shape, pagination, or any limitations. While the core purpose is clear, the absence of an output schema places more burden on the description to explain return values, which it only partially does.

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 provides 100% coverage for the single parameter courseId, including a pattern and description. The tool description adds no additional semantic meaning beyond implying a course context, so the baseline of 3 is appropriate.

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?

Clearly states the action (list) and resource (assignments and tasks in a course), and specifies the included data fields (due dates, scores, submission status). This distinguishes it from sibling tools like blackboard_list_announcements or blackboard_get_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?

The phrase 'in a course' implies the tool is intended for course-scoped listing, but there is no explicit guidance on when to use it vs. alternatives such as blackboard_list_attempts or blackboard_get_grades. No exclusions or alternative tool mentions are provided.

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