list_new_quiz_items

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

Annotations already provide readOnlyHint=true, indicating safe read operation. Description adds that it lists 'all items', clarifying scope. However, no additional behavioral traits (e.g., pagination, rate limits) are disclosed beyond 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?

Single concise sentence with no unnecessary words. Front-loaded with key information (verb, resource, qualifier).

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 the tool's simplicity (list operation with two parameters), the description is nearly complete. It specifies the resource and scope. No output schema is provided, but for a list endpoint the return type is implied; openWorldHint suggests results may be extensive, which is adequate.

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 100% (course_id and assignment_id are fully described in schema). Description does not add any parameter meaning or constraints beyond what the schema already provides.

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?

Description clearly states 'List all items (questions) in a New Quiz (LTI).' It identifies the specific verb ('List'), resource ('items in a New Quiz'), and distinguishes from siblings like 'list_quiz_questions' (for classic quizzes) and other list tools.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., list_quiz_questions for classic quizzes). The description only implies usage for New Quizzes via the resource name, but does not state conditions or exclusions.

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