crowd_configure_rvo

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

With no annotations provided, the description carries the full burden of explaining behavior. It states only that defaults are configured, but does not disclose whether the blueprint is saved or compiled, whether this mutates the asset persistently, or what happens if the blueprint does not exist or lacks a CharacterMovement component.

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 front-loaded with the core purpose. The KB pointer and example are both useful and do not add unnecessary bulk, making it appropriately sized for an agent to scan quickly.

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 tool with nine parameters, no annotations, and zero schema description coverage, the description is too thin. It does not explain the operation's side effects, prerequisites, or how the many optional parameters interact, leaving the agent to guess critical configuration 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%, so the description must compensate, but it only documents blueprint_name through the example path format. The remaining eight parameters, including meaningful defaults like groups_to_avoid and consideration_radius, are left entirely to the schema's titles and defaults without any added semantic context.

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 identifies the action (Configure), the target (Character Blueprint), and the subsystem (CharacterMovement RVO avoidance defaults). It is distinguishable from the sibling crowd_configure_detour because it specifically names RVO avoidance, though it does not explicitly contrast itself with that tool.

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?

No guidance is given about when to use this tool versus alternatives such as crowd_configure_detour or other crowd/navigation configuration tools. The KB reference is too generic to serve as usage direction, and the example only demonstrates syntax, not selection criteria.

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