get_usd_prim_stats

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

With no annotations, the description carries the full transparency burden. It explicitly lists the output components (child count, attr count, active, payload), which fully discloses what the tool returns. It does not mention side effects, but this is a read-only stat query, so no side effects are expected.

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, well-structured sentence that front-loads the core purpose and lists specific stats. Every word contributes value with no redundancy or filler.

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, but the description is incomplete due to the unexplained 'path' parameter and lack of any output schema. It does not provide enough context for a correct invocation, especially regarding the distinction between the two parameters.

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?

The schema provides no parameter descriptions (0% coverage), and the description does not explain the meaning of 'path' or 'prim_path'. 'path' is especially ambiguous (could be a USD file path or node path), and the description offers no clarification, leaving the agent unable to correctly infer parameter semantics.

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 action ('Get stats') and the resource ('a USD prim'), and enumerates the specific stats returned (child count, attr count, active, payload). This distinguishes it from sibling tools like get_usd_attribute or list_usd_prims.

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 implies use when needing prim-level stats, but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention any alternative tools. Although the context is clear, the absence of exclusions or alternatives keeps it at a basic level.

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