Remove an uploaded document from your session by providing its unique ID. Delete unwanted files to keep your study materials organized and focused on preparing for the Chilean bar exam.
Quita un documento cargado.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
v0.9.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden of behavioral disclosure. It only says 'quita' and does not state whether the removal is destructive, reversible, requires ownership, or affects associated data.
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 one short sentence with no filler, and the action is front-loaded. It is concise, though slightly under-specified, which prevents a 5.
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 removal tool with no output schema and no annotations, an agent would need to know side effects, success behavior, and any restrictions. The one-parameter schema makes the call simple, but the description is minimal and leaves important context missing.
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 0% and the description does not mention the id parameter explicitly. It only implies that the target is a loaded document, which is minimal compensation for the undocumented parameter.
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 uses the verb 'Quita' (removes) with the resource 'un documento cargado', clearly conveying the tool's action. It is distinguishable from sibling tools like quitar_manual by the resource type and from cargar/leer/listar_documentos by the operation. However, 'quita' could mean delete or unload, leaving some ambiguity.
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 provided on when to use this tool versus alternatives. It does not mention that it applies to loaded documents while quitar_manual applies to manuals, nor does it state prerequisites like the document needing to already exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.