get_usd_generated_component

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real context beyond them: the not-an-error semantics of present:false and the fact that it wraps a specific native API, which helps an agent reason about failure behavior.

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?

Front-loaded with the core purpose, then the error-behavior clarification, then the return shape. The Returns block is justified because no output schema exists, so it isn't redundant. Minor duplication of component_class across the prose and the Returns block is the only waste.

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?

With no output schema, the description correctly carries the return-shape burden via the explicit Returns block. Combined with annotations covering the safety profile and the description covering error semantics, it is nearly complete; a note on when the component can be stale/regenerated would close the remaining gap.

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 100% (both prim_path and actor_path are documented in the schema with examples), so the baseline is 3. The description adds no format or syntax detail beyond 'for a given prim path', so no credit above baseline.

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?

States a specific verb ('Resolve') and resource ('transient USceneComponent generated by the stage actor for a given prim path'), and even names the underlying native API (AUsdStageActor::GetGeneratedComponent) to anchor it. This is clearly distinguishable from siblings like get_usd_generated_assets or get_usd_prim_info, though it does not explicitly name those 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?

It explains the outcome condition (present:false when the path is invalid or the prim has no generated component) and that the caller can 'pivot' on it, which is useful. However, it never states when to reach for this tool versus the sibling get_usd_generated_assets (component vs asset) or other USD query tools, so usage is only implied.

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