manage_level

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

Annotations already flag destructiveHint=true and readOnlyHint=false. The description adds context about the tool's scope (streaming, World Partition, lighting) beyond annotations, but it does not disclose the nature of destructive actions (e.g., delete, cleanup) or side effects. It does not contradict annotations.

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 sentence with no fluff, covering the main operations. It is efficiently front-loaded but is high-level and could be more actionable by mentioning the action parameter or specific sub-capabilities.

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 37 parameters and 24 actions, this description is far too brief. It omits the required 'action' parameter, operation-specific details, return values, and side-effect warnings. The schema carries most of the burden, but the description does not integrate or highlight the most important decision points for an agent.

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 coverage is 59% and includes descriptions for many parameters, but the description does not explain the required 'action' parameter or how to choose among the 24 action values. It vaguely groups some parameters (e.g., lighting, streaming, cells) but provides no direct parameter semantics beyond what the schema already offers.

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 tool handles level-related operations: load/save, streaming, World Partition cells, and lighting. It uses specific verb+resource pairs, but it does not differentiate from sibling tools like manage_lighting or manage_level_structure, which overlap in lighting and structure management.

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. There are no exclusions, prerequisites, or explicit alternative tool mentions, leaving the agent to infer usage from the broad capability list.

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