list_usd_prims

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that the operation is read-only, whether it has side effects, or any performance or permission characteristics; only the bare action is given.

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 front-loaded sentence with no wasted words. However, its extreme terseness leaves essential parameter and usage context unstated, which is a completeness issue rather than a conciseness issue.

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, but the description still omits parameter meaning, usage guidance, and any behavioral attributes. With no annotations and 0% schema description coverage, it is insufficient for a three-parameter USD listing 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?

Schema description coverage is 0%, so the description must compensate for the three undocumented parameters. It hints at the depth parameter ('up to a given depth') but gives no meaning for the required 'path' parameter or the 'root_prim' parameter, nor does it explain defaults.

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 and resource (list USD prims) plus a scope qualifier (up to a given depth). It is understandable without opening the schema, but it does not distinguish the tool from sibling USD prim-listing tools such as lop_prim_search or get_usd_prim_stats.

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?

The description provides no guidance on when this tool should be used instead of alternatives, even though many sibling tools operate on USD prims. There are no exclusions, prerequisites, or routing hints for the agent.

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