find_usd_prims

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

With no annotations, the description carries the full burden, but it only states 'Search USD prims by path pattern' without disclosing return values, search scope, case sensitivity, handling of no matches, or whether results are prim paths or prim data. The read-only nature is implied but not stated.

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 minimal and well-structured: a one-sentence summary followed by a concise Args list. Every sentence adds value, and the essential information is front-loaded.

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 tool is simple with two required parameters, and the description covers both parameters adequately. However, without an output schema or annotations, the missing return behavior (list of paths vs prims, empty result behavior) leaves a notable gap for an agent invoking the 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 coverage is 0%, but the description's Args section adds meaningful semantics: 'node_path' is clarified as 'LOP node path' and 'pattern' is expanded with 'Glob pattern (supports *, **) or substring'. This compensates well for the schema's lack of descriptions.

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 the tool searches USD prims by path pattern, with a specific verb ('Search'), resource ('USD prims'), and mechanism ('path pattern'). It distinguishes itself from siblings like list_usd_prims through the pattern-based scope, though it does not explicitly name alternatives.

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 explicit guidance is given on when to use this tool versus siblings such as get_usd_prim or list_usd_prims. The usage context is only implied by the name and the short description; there are no when-not-to-use instructions or alternative recommendations.

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