set_usd_attribute

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

No annotations are provided, so the description carries the full burden. It only states 'Set a USD attribute value' without disclosing side effects, whether it creates or modifies an existing LOP node, reversibility, or network implications. 'Connect after' hints at network construction but leaves behavior ambiguous.

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 front-loaded with the core purpose in one sentence, followed by a compact parameter list with no fluff. Every line earns its place, and the structure is easy to scan.

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?

As a mutation tool with no annotations and no output schema, the description should provide richer behavioral context. It fails to explain whether a new LOP node is created or an existing one is used, how attribute types are handled, or typical usage flow. The parameter list helps, but overall context is incomplete.

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 provides one-line explanations for all four parameters, adding value beyond the schema's bare titles. Notably, 'node_path: LOP node path to connect after' clarifies the parameter's role, which is not obvious from the name alone.

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 specific verb ('Set') and resource ('USD attribute value') and adds the implementation mechanism ('via an inline Python LOP'). It is clear and distinct from siblings like set_parameter or set_detail_attrib, though it does not explicitly name alternatives.

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 for USD attribute modification, which is clear from context. However, it gives no explicit guidance on when to prefer this tool over alternatives (e.g., set_parameter for Houdini parameters, set_detail_attrib for geometry attributes) and no exclusions or prerequisites.

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