get_prim_intrinsics

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get intrinsic values' with no information about return format, possible errors, side effects, or how prim_index affects the result. This is insufficient for a tool with zero structured metadata.

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 short sentence, which is efficient, but it is under-specified rather than concise. It omits essential context, so the brevity is a negative trait here.

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, no annotation coverage, and minimal description, the tool lacks complete context. There is no explanation of return values, error behavior, or parameter interactions, making it inadequate even for a simple 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%, and the description does not mention either parameter (node_path, prim_index). It adds no meaning beyond the parameter names, failing to compensate for the missing schema descriptions.

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 uses a specific verb ('Get') and resource ('intrinsic values of a primitive'), which clearly identifies the tool's core function. It distinguishes from siblings like get_prims or get_attrib_values by focusing on intrinsics, a distinct concept in Houdini.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention sibling tools, prerequisites, or any use case context, leaving the agent to infer that it is for retrieving intrinsic values without any differentiation from related getter tools.

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