setSchematicUiSingleWindow

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions setting a boolean without explaining effects on UI state, prerequisites, or side effects (e.g., whether it requires an open schematic).

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, which is concise, but the grammatical issues ('opens reuse') reduce clarity. It could be restructured for better readability without adding length.

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?

The tool is simple with one parameter and an output schema, but the description lacks sufficient context about when to set single window mode and what impact it has on the UI. A complete description would explain the behavior change.

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?

For the single boolean parameter 'enabled', the description adds some meaning by associating it with 'reuse a single live schematic path'. However, this is vague, and schema description coverage is 0%, so the description should be clearer to compensate.

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 the tool sets a boolean for single window behavior, but the phrasing 'opens reuse' is awkward and unclear. It distinguishes from siblings like setLtspiceUiEnabled, but the purpose is only moderately clear.

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 setLtspiceUiEnabled or other UI tools. Absence of context leaves the agent uncertain about appropriate invocation scenarios.

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