add_quiz_questions

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

No annotations are provided, so the description carries the full burden. It discloses the upsert behavior (a question with the same `name` is updated in place) and details the exact structure for all four question types. It does not mention broader side effects or permissions, but the given behavior is substantial.

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 compact and well-structured: a single introductory sentence with the upsert rule, followed by a concise list of question types and their fields. Every sentence adds value, and there is no redundancy.

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?

Despite having no annotations or output schema, the description provides all necessary information to construct valid arguments: the upsert rule, the four question types with their required fields, and the note that `text` is HTML. The `course` and `quiz_id` parameters are self-explanatory. The description is complete for practical use.

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 schema only provides parameter names with no descriptions. The description fully compensates by detailing the `questions` parameter with per-type field specifications (choices, correct, etc.), which is essential because the schema allows additional properties and lacks structure. This goes well 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 opens with 'Add or update questions', which clearly specifies the verb (add/update) and resource (questions). It further distinguishes itself by describing the upsert-by-name behavior, separating it from sibling tools like list_quiz_questions or 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?

The description clearly implies this tool is for creating or modifying questions in a quiz, which sets a clear context. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous and no exclusions are needed.

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