get_new_quiz_item

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description confirms the read operation and specifies the source (New Quiz LTI) and identifier (item ID), but does not disclose additional behaviors such as error responses, authentication requirements, or what happens if the item is not found.

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, front-loaded sentence that efficiently communicates the tool's purpose without any redundant or extraneous information.

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 (3 parameters, no output schema, annotations covering read-only/open world), the description is adequate but could be improved by mentioning the return value structure or typical response fields, which are not described elsewhere.

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?

All three parameters have descriptions in the input schema (100% coverage), so the description adds no additional meaning. It implicitly reinforces the use of item_id as an identifier but does not elaborate on formats or constraints beyond 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 clearly states the action (Get), the resource (a single item/question from a New Quiz), and the key identifier (by item ID). It distinguishes this tool from siblings like list_new_quiz_items and create_new_quiz_item.

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 implies usage when a specific item is needed by ID, but provides no explicit guidance on when not to use it or alternatives like list_new_quiz_items for browsing. Given sibling tools for listing, creating, updating, and deleting items, additional context would be helpful.

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