lop_prim_get

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

No annotations are provided, so the description carries the full disclosure burden and does not meet it. It implies a read via 'Get' but says nothing about behavior on an invalid prim path, whether a stage must be active, or what 'details' encompasses.

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 short sentence with no padding and the purpose front-loaded. It is efficient, though the brevity is under-specification rather than deliberate concision.

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 described. Still, with three undocumented parameters, no usage guidance, and no annotations, the definition leaves critical invocation details unresolved for what appears to be a simple lookup tool.

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?

Three parameters at 0% schema description coverage, and the description explains none of them. The distinction between the required 'path' and 'prim_path' is particularly unclear and undocumented anywhere, so the description fails to compensate for the coverage gap.

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 states a clear verb ('Get') and resource ('details of a specific USD prim'), so the basic purpose is legible. However, it offers no differentiation from closely related siblings such as get_usd_attribute, get_usd_prim_stats, or lop_prim_search, and 'details' is vague about what is actually returned.

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 guidance on when to use this tool versus get_usd_attribute, get_usd_prim_stats, or list_usd_prims. No preconditions (e.g. a loaded stage) or exclusions are stated, leaving the agent to infer selection from the name alone.

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