edubase_delete_quiz_grading_preset

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

Annotations already indicate destructiveHint and idempotentHint, and the description adds concrete failure conditions: global presets, organization presets, and presets in use by a Quiz or exam cannot be deleted. This goes beyond the structured fields by explaining the boundaries of the deletion behavior.

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?

Two sentences, with the action verb and object front-loaded and the constraints in a compact second sentence. No wasted words.

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 simple one-parameter delete operation, annotations supply the destructive/idempotent profile and the description supplies the key constraint set. The agent has everything needed to select the tool, provide the preset ID, and predict failure conditions.

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 single parameter 'preset' is fully documented in the schema as 'grading preset identification string', and the description doesn't add any further syntax, format, or source guidance. With 100% schema coverage, a baseline of 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?

States a specific verb and resource: 'Remove a custom grading preset.' The qualifier 'custom' differentiates this deletion from global or organization presets and from sibling tools such as get_quiz_grading_preset, post_quiz_grading_preset, and patch_quiz_grading_preset.

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 provides clear scope by listing three categories that cannot be removed, which tells the agent when the tool will fail. It does not explicitly name alternative tools or route to get/patch operations, so it stops short of a full when/when-not guide.

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