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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the leading "Read-only" adds little. The valuable additions are the implicit auth scoping (only the signed-in maker's own quizzes, with no user filter available) and the return-field inventory, which matters because there is no output schema; pagination, ordering, and empty-list behavior remain undisclosed.

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?

Two short sentences, front-loaded with the operation, then the return shape, then the decision rule. Nothing is redundant beyond the minor restatement of "read-only" already carried by the annotations.

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 zero-parameter, non-destructive list tool with no output schema, the description supplies scope, the returned fields, and a usage rule — everything needed to call it correctly. The only omission, result ordering or paging, is a minor edge concern rather than a blocker.

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, so there is no parameter semantics to document and the baseline is 4. The description correctly devotes no space to argument explanation.

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 ('quizzes') with an explicit scope: "the signed-in maker's quizzes." It also enumerates the returned fields (id, title, version, question count, test/live status), so an agent knows exactly what it gets without opening a schema, and the routing sentence separates it from create_quiz.

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 this to continue an existing quiz instead of creating a duplicate" gives a concrete when-to-use plus the competing action it should replace. It stops short of naming the other relevant siblings (get_quiz, update_quiz) or saying when listing is not the right call, 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.