get_prims

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a safe, non-mutating operation and the pagination mechanics (200 default, has_more loop) are usefully disclosed, but there is no mention of return shape, attribute types, permissions, or limits beyond page size.

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 leading sentence is front-loaded and the Args block is easy to scan. The per-parameter lines verge on restating field names, but overall it is appropriately sized with no wasted prose.

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 and no annotations, the description should do more work. It implies a has_more cursor in the response and documents paging, but leaves return values, attribute behavior, and error/precondition cases unspecified for a 5-parameter read 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 description coverage is 0%, so the description must compensate. It lists all five parameters and adds real meaning for count/start/pagination, but node_path ('Node path'), start ('Start index'), and group ('Prim group filter') are thin restatements of the field titles rather than syntax or format guidance.

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 and resource ('Read primitive data and attributes') plus a pagination scope. It does not name or distinguish itself from the many closely related siblings (get_points, get_prim_intrinsics, sample_geometry, get_usd_prim), so an agent gets a clear action but no explicit differentiation.

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 'page on with start while has_more is true' note is a usage detail for pagination, but there is no guidance on when to choose this tool over get_points, get_prim_intrinsics, or the USD prim readers. No prerequisites or exclusions are stated.

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