list_assignments

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety behavior is well covered structurally. The description's 'Read' matches those annotations and adds return-content context, but it does not discuss pagination, ordering, or error 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 one efficient, front-loaded sentence. Every phrase adds value by specifying either the resource or the fields returned, with no filler or repetition.

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 one-parameter list tool, the description covers the purpose, the required parameter input, and the principal return fields despite lacking an output schema. It would benefit from a note on scope or pagination, but the absence is minor for this simple read operation.

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 is the main source of parameter meaning: it defines courseId as an exact Brightspace numeric identifier from another tool and supplies a pattern. The description adds no additional parameter information, so the baseline for high schema coverage applies.

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 the verb 'Read' and names the resource ('assignments'), and then enumerates the useful return fields: instructions, due dates, closing times, and attachment IDs. It is clear, but it does not explicitly distinguish itself from the sibling get_assignment for retrieving a single assignment.

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 about when to use list_assignments rather than get_assignment, list_official_grades, or other course-related tools. The correct usage context must be inferred entirely from the tool name and brief description.

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