Create New Quiz Item

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

Annotations already signal potential side effects via destructiveHint and openWorldHint. The description adds valuable context beyond those flags by disclosing Canvas rate-limit behavior and instructing serial execution, which is not derivable from the schema or annotations.

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 short sentences, each earning its place: the core action, supported types, rate-limit warning, and batching guidance. The most important scoping information is front-loaded and there is no redundant phrasing.

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?

The description is adequate for a create operation with a detailed input schema and explicit rate-limit handling. It omits return-value expectations, but no output schema exists and the core call contract is well covered by the schema and description combined.

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 80%, so the schema carries most parameter semantics. The description adds a helpful mapping of the 5 supported item types, but does not meaningfully elaborate on parameters like points_possible, course_id, or assignment_id beyond what the schema already documents.

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 action ('Create an item (question)'), the exact resource ('New Quiz (LTI)'), and enumerates the five supported item types. It clearly distinguishes this from sibling tools like create_new_quiz (quiz-level creation) and update_new_quiz_item (modification).

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 gives concrete operational guidance: call serially, avoid parallel calls, and chunk batches over 50 items with pauses due to Canvas rate limits. It does not explicitly mention alternatives like update/delete/list new_quiz_item, but the serialization and batching guidance is clear and actionable.

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