edubase_patch_quiz

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description doesn't need to restate those. The description adds value by clarifying the scope of the update (only the listed fields) and by pointing to sibling tools for other operations. However, it doesn't disclose details like whether partial updates are supported, whether the 'quiz' parameter is required as an identifier, or what happens if the quiz doesn't exist. The description is consistent with annotations, and the idempotentHint is supported by the patch semantics implied by the description.

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 two sentences long, with the primary purpose front-loaded in the first sentence and the routing guidance in the second. Every word earns its place: the first sentence lists the exact fields, and the second sentence prevents misuse by naming the correct sibling tools. There is no fluff, repetition, or unnecessary detail.

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 patch tool with six parameters, 100% schema coverage, and no output schema, the description is quite complete. It tells the agent what the tool does, which fields it updates, and which sibling tools to use for related operations. The only minor gap is that it doesn't explicitly state that the 'quiz' parameter is required (though the schema marks it as required) or describe the return value, but the schema covers the required parameter and the lack of an output schema makes return-value documentation less critical. The routing to siblings is a strong contextual addition.

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 100%, so the schema already documents all six parameters. The description adds value by summarizing the purpose of the tool as updating title, external identifier, language, description, and organization, which maps directly to the parameters. It also clarifies the relationship between the 'id' parameter (external identifier) and the 'quiz' parameter (quiz identification string) by calling the former 'external identifier' in the description. However, the description doesn't add much beyond the schema's own parameter descriptions, so a 4 is appropriate rather than a 5.

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 verb ('Update'), a specific resource ('existing Quiz set'), and enumerates the exact fields that can be changed (title, external identifier, language, description, organization). It also distinguishes itself from sibling tools by explicitly naming edubase_post_quiz_settings and edubase_post_quiz_questions as the tools for settings and questions, respectively. This makes the tool's purpose unambiguous and clearly differentiated from the many quiz-related siblings.

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 explicitly says when to use this tool (to update quiz set details) and when to use alternatives: 'Use edubase_post_quiz_settings to change its settings and edubase_post_quiz_questions to add questions.' This is a clear routing instruction that prevents an agent from confusing this patch tool with the settings or questions tools. It also implicitly excludes deletion (edubase_delete_quiz) and creation (edubase_post_quiz) by focusing on updating an existing quiz.

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