get_usd_prim_stats

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 disclosure, and it does little. It does not say whether the count is recursive, how USD type taxonomy is determined, how instance proxies affect results, or what the return shape is. Only the vague scoping hint 'under a root path' adds behavioral context beyond the schema.

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?

A single short sentence, so nothing is wasted, but it is under-specified rather than concise. It front-loads the verb and resource, though the trailing prepositional phrase is the only qualifier available.

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 is short for a three-parameter tool with zero schema coverage and no annotations or output schema. It conveys the core purpose adequately, but an agent would lack necessary detail on parameter meaning and result format to call it confidently.

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%, with three parameters and only titles like 'Node Path', 'Prim Path', and 'Traverse Instance Proxies'. The description mentions 'root path' ambiguously, leaving unclear whether it maps to node_path (required) or prim_path (default '/'), and traverse_instance_proxies is entirely unaddressed.

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 verb and resource: counting prims grouped by USD type under a root path. That is more specific than the name alone, but it omits scope details and does not distinguish it from siblings like get_usd_prim, get_attrib_stats, or find_usd_prims, so an agent must infer how this differs from a plain prim lookup.

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 when-to-use guidance is given, no prerequisites, no exclusions, and no alternatives are named. The 'under a root path' phrasing implies recursive scoping but does not say whether to use this instead of find_usd_prims or get_usd_prim for counting versus listing.

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