get_related_ue_systems

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

No annotations are present, so the description alone must disclose behavior. It indicates a read operation ('Get') but gives no details about the nature of the relationships, whether the input system is included in results, or the direction of the relation. This leaves significant ambiguity for the agent.

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 a single concise sentence with no extraneous words, front-loading the main action. It is appropriately short, though a bit more detail could enhance clarity without bloating the text.

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 no output schema, no annotations, and the ambiguity of 'related', the description is incomplete. It fails to explain the return format, the types of relationships, or any edge cases, which is important for effective 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?

The only parameter, systemId, is well-described in the schema with 'System ID to find related systems for', achieving 100% schema coverage. The description adds no additional parameter context, but the baseline of 3 applies because the schema already explains the parameter's meaning.

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 states the action ('Get systems') and the target resource ('related to a specific Unreal Engine system'), matching the tool name. However, it does not explain what 'related' means, which could be ambiguous with siblings like 'get_class_hierarchy' or 'get_asset_dependencies'.

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 usage context is provided. The description does not indicate when to use this tool versus alternatives, when not to use it, or any prerequisites. With many sibling tools that could also return related information, the lack of guidance is a clear gap.

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