lop_layer_info

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing beyond 'Get ... info'. It does not state that the operation is read-only, whether it requires an open USD stage or an existing LOP node, or what happens if the path is invalid.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity contributes to the missing detail noted elsewhere.

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?

An output schema exists, so return values need not be explained. However, with no annotations and an unspecified 'path' parameter, the definition leaves the agent guessing about both the input's meaning and how this tool differs from the other USD-inspection siblings.

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% for the single 'path' parameter, and the description does not compensate: it is ambiguous whether 'path' is a Houdini node path (e.g. /stage/lop) or a USD primitive path. This ambiguity matters for correct invocation.

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?

States a specific verb ('Get') and resource ('USD layer stack info') scoped to a LOP node, so the agent knows it is a read of layer-stack data rather than stage or prim data. It does not, however, distinguish itself from close siblings such as lop_stage_info, get_usd_composition, or inspect_usd_layer, which plausibly overlap.

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?

There is no when-to-use guidance, no exclusions, and no named alternative. Given several siblings that surface USD information (lop_stage_info, get_usd_composition, inspect_usd_layer, list_usd_prims), the absence of routing guidance is a real gap.

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