ue_new_level

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

Without annotations, the description must bear the burden of behavioral disclosure. It only states creation and opening but omits critical details like whether existing levels are overwritten, required permissions, side effects on project state, or error conditions. This is insufficient for safe tool invocation.

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 extremely concise with two bullet points and no redundant information. It front-loads the main action. However, it could be slightly more detailed without losing conciseness, hence a 4 rather than 5.

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 simplicity (2 params, no output schema, no annotations), the description covers the basic operation but lacks completeness regarding error handling, default template behavior, and relationship to sibling tools. It is minimally viable but not comprehensive.

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. It provides brief explanations: path is the full level path, template is an optional source level to duplicate. This adds meaning beyond the schema types but lacks format specifics or constraints (e.g., valid extensions). A 3 reflects adequate but not thorough param guidance.

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 'Crea un nuovo livello e lo apre' clearly states the verb (create and open) and resource (new level). It distinguishes from sibling 'ue_open_level' which opens an existing level, so purpose is unambiguous.

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 on when to use this tool versus alternatives like 'ue_open_level' or 'ue_save_all'. The description does not specify prerequisites or contexts where creating a level is appropriate, leaving the agent without decision support.

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