get_quiz_question_responses

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

Beyond annotations (readOnlyHint, openWorldHint), the description discloses that failed per-submission fetches are recorded in submissions_failed instead of aborting, and student names may be pseudonymized. It also mentions the per-submission API call cost and the reporting of needs_manual_grading and points_possible.

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 a single, well-structured paragraph that leads with purpose, then constraints, usage, and behavioral details. It is reasonably concise for the amount of information, though slightly denser than necessary.

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 no output schema, the description adequately explains response features (needs_manual_grading, points_possible), error handling, privacy behavior, and performance implications. It covers all essential contextual information for a read tool.

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%, so baseline is 3. The description restates parameter usage (omit question_id for all, provide to scope) but does not add new meaning beyond what is in the schema.

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 specifies retrieving student responses to Classic Quiz questions, pivoted by question, for grading consistency. It clearly distinguishes from sibling tools by explicitly stating 'Classic Quizzes only' and contrasting with New Quizzes.

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 explains when to use (for grading essay/short-answer/file-upload questions across a class) and when not to (New Quizzes). It also clarifies parameter usage: omit question_id for all questions or provide to scope to one. Missing explicit alternative tool name, but the guidance is sufficient.

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