remove_submission

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to repeat that. It adds context that deletion is conditional on Moodle version and permissions, which is useful. However, it doesn't explain failure behavior or impacts beyond deleting, so the added value is moderate.

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 clear sentence, front-loaded with the action. No fluff or repetition. It earns full marks for brevity, though it lacks structured breakdowns.

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 destructive tool with 3 parameters (2 required) and no output schema, the description is insufficient. It doesn't mention the confirmation_token's purpose, how to obtain it, or what happens on failure. An agent would need to rely on other tools (like preview_remove_submission) without any guidance.

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 coverage is 0%, so the description must explain parameters. It doesn't mention confirmation_token at all and only implies assignment_id as the target. No explanation of course_module_id's role. This is a significant gap for a tool with two required parameters.

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 action ('Elimina una entrega completa') and resource (a submission), making the purpose clear. It also adds a condition (version and permissions). However, it doesn't explicitly distinguish from sibling deletion tools like delete_submission_files, so it's not a 5.

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?

No guidance is given about when to use this tool versus alternatives. The condition mentioned (version and permissions) is about whether the deletion can happen, not about tool selection. There is no mention of prerequisites (like needing a confirmation_token from a preview) or when to avoid this tool.

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