inspeccionar_jerarquia_escena

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

There are no annotations, so the description carries full responsibility for behavior disclosure. It implies a read-only analysis by saying 'Analiza' and 'devuelve', but it does not clarify whether an engine instance must be running, whether files are only read, or what side effects might occur.

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 entire description is one focused sentence with no filler. It is concise and front-loaded with the core action, though it could benefit from a short usage or behavior note.

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 two-parameter inspection tool, the description gives an adequate high-level view of the return value. However, with no output schema and no annotations, details about the exact hierarchy format and prerequisites are 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 coverage is 100%, so the parameters are already well documented. The description adds only mild context about Unity/Godot and scene files, but does not significantly enrich meaning beyond the schema.

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 a specific verb ('Analiza') and resource ('escena o mapa actual del motor (Unity/Godot)'), clearly stating that the tool returns the object/node/component hierarchy. It is easily distinguished from siblings like ejecutar_suite_pruebas_motor or escribir_codigo_seguro.

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 choose this tool over alternatives, nor any exclusions or prerequisites. The agent must infer from the sibling names that this is the inspection tool.

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