List My Quiz Submissions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the 'Read-only' sentence is largely redundant. The description does add one piece of behavioral value beyond annotations—that the result includes a score per attempt—but says nothing about result count, pagination, or ordering.

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?

Three short sentences, zero filler, with the scope ('all attempts … score for each') front-loaded before the sibling routing hint.

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 carries some burden of describing returns and does so minimally ('the score for each'). For a simple two-parameter read tool that is nearly sufficient, though ordering/pagination and empty-result behavior remain unstated.

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%: both course_id and quiz_id are documented in-schema, including where to obtain the IDs (list_courses, list_quizzes/list_new_quizzes). The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

States a specific verb ('List') and resource ('your attempts on a quiz') plus the returned payload ('the score for each'), which lets an agent distinguish it from get_my_quiz_submission 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?

'Use get_my_quiz_submission for just the latest' explicitly names the alternative and the condition that selects it. It stops short of a full when/when-not pair (e.g., no guidance on paging or when scores are unavailable pre-grade), so it is clear but not exhaustive.

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