lop_stage_info

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Get' implies a read-only operation and it names the categories of data returned, but it omits output format, permissions, performance implications, and whether reading triggers stage evaluation.

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 tight sentence with no filler. The purpose and the three main data categories are front-loaded and efficiently conveyed.

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?

Has an output schema but the description never references it, and the required path parameter is undocumented. It gives a rough sense of scope via prims, layers, and time codes but leaves sibling overlap and invocation details unaddressed.

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 single 'path' parameter is never described in the description or schema. The phrase 'from a LOP node' hints that path identifies a LOP node, but expected format or example is absent.

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?

Specifies a clear verb and resource: get USD stage info from a LOP node, and lists the returned components (prims, layers, time codes). However, it does not differentiate from overlapping siblings such as lop_layer_info or list_usd_prims, leaving the agent to infer that this is a broad stage-level snapshot.

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 given on when to use this tool versus lop_layer_info, list_usd_prims, get_usd_composition, or inspect_usd_layer. The description implies a stage-scope overview, but provides no explicit when/when-not or alternative selection conditions.

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