ue_engine_templates

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

The description implies a read-only listing operation by using 'elenca' (lists), but does not explicitly state safety or side effects. With no annotations provided, the description moderately covers behavior adequacy but lacks detail on requirements or restrictions.

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 that front-loads the core purpose. Every word is necessary, and there is no redundant information.

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 the tool has two undocumented parameters and no output schema, the description should at least hint at parameter meaning or return format. It omits this entirely, leaving the agent underinformed for proper 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 description does not mention the two parameters (engine_root, engine_version) that are optional with defaults. Schema coverage is 0%, so the agent has no clue what these parameters do or how to use them, which is a critical gap.

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 it lists official templates available in the installation, with specific examples like TP_Blank and TP_ThirdPerson. This distinguishes it from sibling tools like ue_engine_list, which likely list engines rather than templates.

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 provided on when to use this tool versus alternatives such as ue_engine_list or preset_search_polyhaven. The agent receives no context for selecting this tool over others.

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