preview_replace_submission_files

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'no sube nada'. It adds the behavior of validation ('valida'), which is not in the annotations, providing additional context about what the tool does.

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?

One concise sentence that is front-loaded with the verb, 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?

The description is too brief for a tool with three parameters and no schema descriptions. It lacks explanation of parameters, potential errors, or the nature of the validation. While the naming and annotations help, the description leaves the agent to guess parameter meanings.

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%, but the description does not explain any of the three parameters. It mentions 'archivos' which loosely maps to file_paths, but gives no guidance on assignment_id or course_module_id. This is a significant gap given the zero coverage.

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 clear purpose: to validate and preview the replacement of files, explicitly noting it does not upload anything. This differentiates it from sibling tools like replace_submission_files and preview_delete_submission_files.

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 implies it is for previewing before an actual replacement, and the phrase 'no sube nada' distinguishes it from the execution tool. However, it does not explicitly name the alternative or state when exactly to use it versus other preview tools (like preview_delete_submission_files).

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