edubase_patch_quiz_settings

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

Annotations already mark this as idempotent and non-destructive. The description adds meaningful behavioral context by specifying that only settings not yet configured are copied, meaning existing target settings are preserved. This goes beyond the annotation hints and clarifies the merge semantics.

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 sentence with no wasted words. The core action ('Copy') and the distinguishing condition ('not configured yet') are front-loaded, making it immediately actionable for an agent.

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 two-parameter, idempotent, non-destructive operation with an output schema, the description covers the essential invocation semantics. It does not specify behavior when no settings are missing or the exact list of copied settings, but those details are not required for correct tool selection and invocation.

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%, with both parameters fully described: 'quiz' as the target and 'source' as the copy source that must differ from the target. The description adds no additional parameter-level detail beyond what the schema already provides, so the baseline 3 is appropriate.

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 ('Copy'), a specific resource ('settings from another Quiz set'), and the precise condition ('not configured yet in the target Quiz set'). This clearly distinguishes it from sibling tools like edubase_get_quiz_settings, edubase_post_quiz_settings, and edubase_put_quiz_settings.

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 intended use case (merging only missing settings from a source quiz into a target quiz) is implied but not explicitly contrasted with alternatives. The description does not state when to use this over edubase_put_quiz_settings or edubase_patch_quiz_settings, leaving the routing decision to the agent's inference.

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