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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description goes beyond them by disclosing side effects: duplicate submissions are skipped, the source Classroom assignment is recorded for later grade export, and only counts are returned. This is useful behavioral context an agent cannot get from the annotations alone.

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?

Four compact sentences, front-loaded with the core action, followed by sourcing, skip behavior, side effects, and return shape. No filler; every sentence carries distinct information.

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 write tool with four required parameters, an output schema, and moderate nested structure, the description covers sourcing, deduplication, export linkage, and return granularity. It is complete enough to call correctly, with only the lack of explicit sibling routing as a minor gap.

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 75% with all five properties described. The description adds meaning beyond the schema by explaining the trade-off between reading an authorized Doc directly versus supplying teacher-provided text, and by clarifying that handles originate from the Classroom roster/list_google_classroom_work.

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 specific verb and resource: adding Google Classroom turn-in handles to a grading session. The Classroom-specific scope distinguishes it from import_essays_from_files and import_essays_from_text, though it never names those siblings explicitly, so an agent must infer the routing.

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 supplies relevant context (names come from the Classroom roster, existing submissions are skipped, and teacher-provided text covers files lacking Google access), which implies when to use it. However, it never states when to prefer this tool over import_essays_from_files or import_essays_from_text, so the selection guidance is left to inference.

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