starwind_add

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

Discloses auto-detection of package manager and Pro components, validation, and init flag behavior. Lacks mention of error handling or output format, but adequate for a command generation tool.

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 concise sentences, front-loaded with purpose. Every sentence adds distinct value: purpose, usage context, and special case for Pro. No verbosity.

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?

Covers main functionality, usage guidance, and special cases for Pro and init. Lacks details on output format and validation failure behavior, but overall complete given no output schema and straightforward 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?

Adds meaning beyond schema by explaining workflow context (use after starwind_docs), auto-detection of pro, and the '--all' special value for components. Schema already covers 100% of parameters, so baseline is 3; description adds value.

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?

Clearly states it generates installation commands for Starwind UI components. Differentiates from siblings like starwind_docs and starwind_init by specifying its role in generating CLI commands.

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?

Explicitly advises using after consulting starwind_docs and explains when to set pro=true, providing clear guidance on when and how to use the tool.

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