app-file_new

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

With no annotations, the description carries the burden. It discloses the in-place nature and the dirty condition, but it does not explicitly state that it discards unsaved changes or that the action is destructive. The lack of detail about side effects is a gap.

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?

Single sentence with no fluff. It front-loads the main action and adds a key condition, making it extremely concise and well-structured.

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 one-parameter tool, the description covers the core function but omits details like what happens to unsaved data without force, potential confirmation prompts, or any return value. Given the destructive nature, more context would be beneficial.

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 adds meaning beyond the schema by specifying when 'force' is needed ('if dirty'). This clarifies the parameter's trigger condition, which the schema's title alone does not fully convey.

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 specifies the action ('Empty the scene in-place') and differentiates from siblings like open/save by focusing on the new/empty operation. It also adds a context cue ('keeps the live bridge'), though 'new file' is not explicitly named.

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 such as app-file_open or app-file_save. The only hint is 'force is required if dirty', which is more about parameter usage than overall context.

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