lop_prim_get

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

No annotations are present, so the description carries the full burden. It notes NO_UNDO and that responses pass through server-side apply_response_cap, which adds context, but it does not disclose error behavior, confirm read-only nature, or elaborate on the response capping's impact.

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 two terse sentences that commit no waste: the first states the core output, the second covers the required parameter and response handling. Every sentence earns its place, making it highly concise.

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 4 parameters, no output schema, and no annotations, the description omits essential context for three parameters and does not position the tool among closely related query siblings. Significant gaps remain for an agent to use it correctly in varying situations.

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%, and the description only explains prim_path with a concrete example. ctx, node_path, and max_attributes remain entirely undocumented, so the description fails to compensate for the schema gap for three of four parameters.

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 that the tool returns type/active/loaded/kind plus bounded attributes for a single prim, making its purpose specific and unambiguous. It distinguishes from sibling query tools like lop_prim_search by targeting a single prim's core properties rather than searching or general stats.

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 usage is for retrieving a specific prim's info and marks prim_path as required, but it does not explicitly compare to alternatives like get_usd_prim_stats or provide when-not-to-use guidance. It gives a prerequisite but no exclusions or alternative conditions.

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