set_usd_attribute

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

With no annotations provided, the description carries the full burden. It discloses the mutating nature (MUTATING), the failure behavior (returns unsupported when mapping is lossy), the prohibition against fallback, accepted attribute_type values, and server-side apply_response_cap. This is substantial behavioral disclosure, though it omits prerequisites and reversibility.

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 compact and every sentence conveys a constraint or type list. It is appropriately sized for the amount of information, though the lack of paragraph breaks makes it somewhat dense. No unnecessary fluff.

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 complex mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It does not explain parameter meanings, value formats, return values, or usage conditions, leaving significant gaps for correct tool invocation.

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 coverage is 0%, and the description adds little. It only clarifies attribute_type accepted values. Other parameters (ctx, parent_path, prim_path, attribute, value, node_name) are unexplained, leaving the agent without essential semantics for correct invocation.

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 uses the verb 'create' and identifies the resource as a whitelist attribute authoring LOP, which differentiates it from generic get/set USD tools. However, the technical jargon (authoring LOP) may be unclear to those not familiar with USD workflows, so it is not a 5.

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 does not explicitly state when to use this tool versus alternatives. It mentions internal constraints (no fallback, unsupported mapping) but gives no guidance on appropriate scenarios or exclusions, so it fails to help the agent choose this tool over siblings.

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