scene_clear

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

With no annotations, the description carries the burden and clearly states the destructive outcome (deleting all pattern pieces or starting a fresh project). It does not disclose reversibility or side effects, but for a simple mutating tool with a single parameter, the statement is sufficient to set expectations.

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?

One sentence, no filler, with the primary action front-loaded. Both branches of behavior are presented compactly without redundancy.

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 a single parameter, no output schema, and straightforward behavior, the description provides everything needed to call the tool correctly. It is self-contained and does not require external context.

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 schema provides only a boolean with a default and 0% description coverage. The description fully explains the semantic difference between true and false, adding critical meaning that the schema lacks entirely.

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?

Description states a clear verb ('Delete'/'start a fresh project') and resource ('all pattern pieces'/'project'), and distinguishes two distinct behaviors via the parameter. It separates itself from siblings like pattern_delete (which targets individual pieces) and scene_open (which loads a scene) by the scope of the action.

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?

The description clearly links parameter values to usage scenarios (keep_avatar=True vs False), indicating when to use each mode. However, it does not explicitly mention alternatives or when to avoid this tool in favor of pattern_delete or scene_open, leaving slight room for ambiguity.

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