get_assignments

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds value by stating what the returned data contains (due dates, submission status, scores) and the scope of an omitted course parameter, but it does not disclose ordering, pagination, or what 'current courses' means.

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 short sentences with zero filler; the main purpose is front-loaded and the usage note about omitting course follows naturally. Every word 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?

For a read-only tool with one optional, fully documented parameter and no output schema, the description covers return content and scoping behavior adequately. The main gap is the lack of differentiation from semantically overlapping siblings like get_upcoming and get_assignment, which an agent must infer on its own.

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 100%, so the baseline is 3. The description's 'Omit course for all current courses' essentially duplicates the schema's 'Course filter. Omit for all current-semester courses' and adds no new semantic detail—it is arguably slightly vaguer.

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 names a specific resource (Brightspace assignments/dropbox folders) and the return contents (due dates, submission status, scores). The plural form distinguishes it from the singular sibling get_assignment, but it never names or contrasts any sibling, so it stops short of the top score.

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 only guidance is 'Omit course for all current courses,' which is a parameter-behavior note rather than tool-selection guidance. There is no indication of when to choose get_assignments over get_upcoming, get_assignment, or get_grades, and no exclusions or prerequisites are mentioned.

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