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 discloses the mechanism (inline Python LOP) but does not address side effects such as node creation, attribute overwriting, reversibility, or permissions. This is insufficient for a mutation tool with zero annotation coverage.

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 action, followed by a compact parameter list. Every sentence serves a purpose with no filler or redundancy.

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?

For a mutation tool with four required parameters, no annotations, and no output schema, the description is too sparse. It omits prerequisites, side effects, error conditions, and what happens when the attribute or node does not exist, leaving the agent under-informed.

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 four parameters, but only node_path adds meaning beyond the schema ('LOP node path to connect after'); prim_path, attr_name, and value largely restate their schema titles. This is minimal viable but leaves format/type nuances undocumented.

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 ('Set') and resource ('USD attribute value'), and the mechanism ('via an inline Python LOP') further clarifies the operation. This distinguishes it from sibling getters like get_usd_attribute and from set_parameter or set_detail_attrib, which target different data domains.

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 provides no when-to-use guidance, no alternatives for similar tasks (e.g., set_parameter), and no prerequisites (e.g., whether a LOP node must exist). The agent is left to infer context entirely.

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