selection_clear

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

With no annotations provided, the description carries the full behavioral disclosure burden. It clarifies that the operation clears selection state in Roblox Studio rather than deleting objects, which is useful, but it does not mention side effects, undoability, or behavior when there is no active selection. Adequate for a trivial operation, but not rich.

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, front-loaded sentence with no filler. Every word contributes meaning, and the clarifying parenthetical earns its place.

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 that the tool has no parameters, no output schema, and a trivial side effect, the description is nearly complete for calling the tool correctly. The only missing dimension is explicit guidance about why to choose clear over related selection mutations, but this is a minor gap for such a simple tool.

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 tool has zero parameters, so parameter-level documentation is unnecessary. The baseline for zero-parameter tools is 4, and the description's parenthetical adds the only relevant semantic nuance.

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 states a specific verb ('Clear') and a precise resource ('the active selection in Roblox Studio'), with the parenthetical 'deselect all' removing any ambiguity. It is clearly distinct from the sibling tools selection_get, selection_set, and selection_add.

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 given about when to use selection_clear versus selection_set, selection_add, or other selection-related tools. The use case is inferable from the name and siblings, but the description does not explicitly state exclusions or alternatives.

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