chaos_inspect_geometry_collection

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

With no annotations, the description carries the full burden, but it only says 'Inspect' and gives an example; the read-only nature and absence of side effects are implied rather than explicit. It does not describe what gets returned or what happens when neither actor_name nor asset is supplied.

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 short and front-loads the core operation before the KB pointer and example. There is no redundant prose, though the KB link includes a long path that could perhaps be trimmed.

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?

An output schema exists, so return details are not the main gap, but the description is still incomplete for a tool with two optional parameters and zero annotation coverage. It does not cover what distinguishes actor/component inspection from asset inspection or how the tool resolves when both are provided.

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 descriptions cover 0% of parameters, so the free-text description must explain them. It offers one actor_name example and implies asset refers to an asset, but it never defines the parameters, their relationship, precedence, or default behavior.

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 names a specific action ('Inspect') and a specific resource type ('Geometry Collection actor/component or asset'), making the tool's basic purpose clear. It does not explicitly differentiate from overlapping inspection tools like get_actor_properties or ue_describe_asset, but the Geometry Collection focus narrows it enough.

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 guidance on when to prefer this tool over alternatives such as chaos_configure_geometry_collection or inspect_static_mesh_sections, nor any explanation of when to use actor_name versus asset. The KB link and example show mechanical usage but do not state selection conditions.

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