eda_sch_select_control_clear_selected

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

No annotations are provided, so the description carries the full burden. It discloses that the operation returns a boolean success flag, but it does not explain side effects (e.g., deselecting all primitives in the current schematic), scope, or whether the action can be undone.

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?

Three short lines with no filler; the signature, Chinese action, and return description are each informative. However, the extreme brevity contributes to missing context scored elsewhere.

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 zero-arg selection-clear operation, the combination of name, signature, and schema covers basic invocation (optional windowId). But it omits explicit confirmation that the selection is in the schematic editor, that args should be empty, and any preconditions.

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 100% at the property-description level, but the descriptions are generic boilerplate ('args' as a JSON parameter array). The method signature 'clearSelected()' adds the useful inference that no arguments are expected, though it does not explicitly state that args should be omitted or empty.

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 'clearSelected() -> boolean' and '清除选中' (clear selection), making the verb and resource clear. However, it largely restates the tool name and does not explicitly differentiate it from sibling select-control tools like get_selected_primitives or do_select_primitives.

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 provides no guidance on when to use this tool versus alternatives. It only states the operation, with no mention of prerequisites, exclusions, or related sibling tools for selection manipulation.

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