eliminar_objeto

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

With no annotations, the description carries the full burden of behavioral disclosure. It only restates the action already implied by the tool name, without mentioning that deletion is irreversible, what happens to child objects, permission requirements, or error behavior. This is insufficient for a destructive tool.

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 concise sentence, front-loaded with the action, and contains no redundant wording. Every word contributes meaning, making it highly efficient.

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?

Despite being a simple tool, it is destructive and lacks annotations. The description omits important context such as effects on the scene hierarchy, error handling, and required preconditions. An output schema exists but is not shown; still, the description alone is insufficient for safe 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?

The schema has 0% description coverage, so the description must compensate. The phrase 'por su ruta' adds meaning by suggesting the 'nombre' parameter is a path, but it doesn't clarify the path format or behavior on invalid input. Partial compensation only.

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 clearly states the action (elimina/deletes) and the resource (objeto de la escena/object from the scene). It distinguishes from siblings like crear_primitiva. However, there is a slight ambiguity: it says 'por su ruta' (by its path) while the schema parameter is 'nombre' (name), which could confuse the identifier type.

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 about when to use this tool versus alternatives, nor about prerequisites such as the object being loaded or the need to use listar_objetos first. The description only states what the tool does, not when to invoke it.

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