create_collision_group

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It reveals that the tool creates a group and returns a read-back, but it does not explain side effects, idempotency behavior, merge semantics, filtering behavior, or any prerequisites. For a mutation tool, this is a significant transparency gap.

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 highly concise and front-loaded, with no filler words. However, it is so terse that it sacrifices parameter and behavior context; conciseness is good, but it borders on under-specification.

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?

Given seven parameters, no annotations, and no parameter coverage, the description is far from complete. The output schema may cover the return value, but the description does not explain the inputs, the nature of the relationship read-back, or how merge/filter options affect behavior.

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 adds no meaning for any of the seven parameters. Required fields like group_path and collider_paths, and optional ones like merge_group_name and filtered_group_paths, are left entirely unexplained, so the agent has no help understanding what values to provide.

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 ('Create') and resource ('USD collision group'), and notes that it returns a relationship read-back. This makes the core action clear, though it does not explicitly contrast with the sibling get_collision_group.

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 intended use is implied by the verb 'Create' — an agent can infer this is the tool to call when a collision group must be created. However, there is no explicit guidance about when not to use it or how it relates to alternatives like get_collision_group.

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