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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds meaningful context beyond that: it requires the teacher's Google Classroom connection and describes the hierarchical traversal and returned handle/link data. It stops short of covering pagination or rate-limit behavior, keeping it from a 5.

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 front-loaded with the core hierarchical behavior, then gives the use case and auth requirement. Every sentence carries necessary information with no redundancy.

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?

Given the simple two-optional-parameter schema, rich annotations, and the presence of an output schema, the description is complete enough for correct invocation. It covers traversal modes, intended use, auth requirement, and returned file handles/links without needing to restate output-schema 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?

Although schema coverage is 100%, the description adds important meaning beyond the schema by explaining how the two optional IDs interact: no IDs yields courses, courseId alone yields assignments, and courseId + courseWorkId yields submission details. This directly clarifies parameter combinations that the schema does not describe.

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 the exact resource and traversal behavior: with no ids it returns the teacher's courses, with a course id it returns assignments, and with both ids it returns submitters and turned-in files. This hierarchical listing is specific enough to distinguish it from generic siblings like list_coursework or list_classes without opening either schema.

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?

It gives a clear usage context: 'Use it to grade typed work collected in Classroom.' However, it does not explicitly name alternatives such as list_coursework, get_submission, or import_essays_from_google_classroom, nor does it state when not to use this tool.

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