electron_generate_window_manager

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

The description indicates the tool generates boilerplate (creating files), which contradicts the annotation 'readOnlyHint: true' that suggests no state modification. This is a serious inconsistency.

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 sentences efficiently convey purpose, features, and patterns with no wasted words. Information is front-loaded and each sentence 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 no output schema, the description does not explain what the tool returns (e.g., files generated on disk or code output). It lacks details on side effects or output format, which is needed for a generator 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?

Schema coverage is 100% with parameter descriptions. The description adds value by explaining patterns (e.g., 'modal dialogs', 'detached panels') and features (inter-window communication, state persistence) beyond the schema.

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 states the tool generates multi-window management boilerplate for Electron apps, specifying the verb 'generate' and the resource 'WindowManager class'. It distinguishes from sibling tools (e.g., electron_generate_preload_bridge) by focusing solely on window management.

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 mentions common patterns (main+child, modal dialogs, detached panels) and implies use in Electron app development. However, it does not explicitly list when not to use or contrast with siblings like electron_scaffold_project.

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