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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, remote-data nature is covered. The description adds one genuinely useful behavioral fact — that the result is scoped to 'this account's submission status' — but says nothing about permissions/enrollment requirements or result size.

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?

A single front-loaded sentence with no filler and no redundancy against the schema. It is efficient, though it is perhaps too terse to carry any routing guidance.

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 read tool with full schema coverage, annotations, and an output schema, this is adequate — return values need not be explained. What is missing is what 'details' covers and whether the account must be enrolled, which an agent would need when deciding between this and list_assignments.

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%, with both course_id and assignment_id documented including their source tools, so the baseline is 3. The description adds no additional parameter meaning beyond what the schema already states.

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 states a concrete verb (get) and resource (one assignment's details) plus a second data dimension (this account's submission status). The singular phrasing implicitly separates it from list_assignments, but it never names that sibling explicitly.

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?

Usage is only implied: 'one assignment' signals this is the per-item drill-down companion to list_assignments. There is no explicit when-to-use, when-not-to-use, or prerequisite (e.g., needing course_id from list_courses and assignment_id from list_assignments).

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