create_collection

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is covered; the description still adds real value by spelling out the idempotent outcome (a stable payload with already_existed=True on repeat calls) and by naming the underlying UE 5.7 ICollectionContainer implementation. It omits any permission/auth requirement or persistence behavior (whether the collection is saved to disk).

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 core sentences are front-loaded and the Returns block is valuable given there is no output schema, but the middle of the description is corrupted — a dangling '"Private", or "Shared".' fragment with no lead-in — which hurts readability. 'Uses the UE 5.7 project ICollectionContainer' is borderline implementation trivia.

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 create tool with no output schema and no annotations covering return shape, the explicit Returns block ({ collection_name, share_type, created, already_existed, exists }) is exactly the missing piece an agent needs. Idempotent semantics are also covered. Remaining gaps are minor: no error/failure behavior and no indication of where the collection is persisted.

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 100%, so the schema already documents collection_name and the share_type values, making 3 the baseline. The description only echoes the share_type options (in a garbled fragment) and adds no new meaning such as validation rules, name-length limits, or whether the name is a path.

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 and resource — 'Creates a static Content Browser collection' — which cleanly separates it from the similarly-named material-parameter collection tools (create_material_parameter_collection) in the sibling list. It is clear on its own, though it never names the sibling tools it pairs with (add_asset_to_collection, get_collections, delete_collection) to complete the routing picture.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the adjacent tools an agent would need (add_asset_to_collection, delete_collection, get_collections). The only routing-adjacent signal is the idempotency note, which describes behavior rather than usage context.

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