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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds important behavioral context beyond annotations: authentication is required, and term selection defaults to the current term when term_id is omitted.

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 two compact sentences with no filler. The main dashboard function and data categories are front-loaded, followed by the optional-term behavior and the authentication prerequisite.

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?

With no output schema, the description still conveys what the tool returns: a summary of deadlines, academic calendar items, and active notices. It also covers auth and the optional term parameter. It is complete enough for an aggregate read-only dashboard tool, though it does not mention error cases or response format details.

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 coverage is 100%, so both term_id and mcp_session_id are already documented. The description adds the requirement to pass mcp_session_id after LMS authentication and reinforces term_id omission behavior, but this largely overlaps with the schema and provides no new parameter-level meaning.

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 clearly states the tool summarizes an authenticated user's LMS dashboard: unsubmitted assignments/quiz deadlines, academic calendar items, and active notices. It is distinguishable from sibling tools like get_my_assignments or get_academic_calendar because it explicitly says it aggregates 'at once,' but it does not explicitly name or contrast those siblings.

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 description gives clear context: it is for authenticated users, requires start_auth via LMS provider, and automatically selects the current term if term_id is omitted. It does not explicitly state when not to use it or which alternative to choose for detailed data, so it stops short of a 5.

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