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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new context: the payload is scoped to the signed-in teacher (implicit auth/identity requirement, no arguments needed) and the cost hint 'Cheap' signals this is a low-latency call safe to make frequently.

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 colon-led sentence front-loads the tool's identity and then lists its contents compactly, with the cost note appended in one word. Nothing is redundant and nothing needed is missing.

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 an output schema present, return values need not be described, and the description adequately frames this as a zero-argument aggregate read for the current teacher. It stops just short of saying anything about freshness or whether the aggregated counts are cached.

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 tool takes zero parameters, which is the baseline case; the description makes clear the scope is derived from the signed-in user rather than from inputs, so an agent understands no arguments are required or expected.

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 concrete aggregation ('Orientation for the signed-in teacher's Fiveable workspace') and enumerates the four content buckets it returns: classes, coursework awaiting review or due, remaining included assignments, and Google connections. That distinguishes it from narrow siblings like list_classes or list_coursework, though it never names those siblings 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?

The word 'Orientation' implies a session-start overview, and 'Cheap' hints it can be called liberally, but there is no explicit statement of when to use this versus list_classes/list_coursework/list_submissions_to_review, nor any exclusion criteria. Usage is inferable rather than stated.

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