list_usd_prims

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

With no annotations, the description carries the burden. It discloses NO_UNDO (non-undoable) and mentions the response cap (apply_response_cap), which are useful behavioral traits. However, it does not explicitly state side-effect status (read-only vs mutating) or any prerequisites, leaving some ambiguity.

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 concise and front-loaded with the core purpose. The parenthetical notes about NO_UNDO and response cap add useful context without excessive length, though the structure could be slightly cleaner.

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?

The description covers the main functionality and return contents, but given no annotations, no output schema, and 0% parameter coverage, it lacks details on required inputs (ctx, node_path) and when to use it. It is adequate for a simple list tool but has clear gaps.

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 description only explains max_depth and max_prims conceptually as limits. It does not clarify ctx or node_path, which are required parameters. The partial insight into two parameters is insufficient for full understanding of all four.

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 clearly states it performs prim traversal limited by max_depth and max_prims, and lists what it returns (paths, names, types, depths). This distinguishes it from sibling tools like get_prim_intrinsics or lop_prim_search, which have different focuses.

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 does not provide guidance on when to use this tool versus alternatives. It only implies its purpose through the traversal limits, but there is no explicit mention of when to prefer list_usd_prims over sibling tools like get_prim_intrinsics or lop_prim_search.

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