sassy_setup_wizard

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

With no annotations, the description carries the transparency burden. It discloses key side effects: writes to ~/.sassymcp/persona.md, installs adb + scrcpy when has_android is true, and installs plink when has_linux is true. It does not mention overwrite behavior or permission requirements, but the disclosed side effects are substantial.

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 front-loaded with the core purpose, followed by a one-line usage instruction and a compact parameter list. Every line adds necessary detail; there is no filler or repetition of schema titles.

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 complex 13-parameter setup tool with no annotations, the description covers purpose, usage, parameter semantics, and side effects. An output schema exists, so return-value details are not necessary, and none of the parameters are left unexplained.

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 description coverage is 0%, but the description compensates excellently. It enumerates allowed values for role, expertise_level, communication_style, and security_posture; specifies comma-separated formats; defines the newline-separated structure for systems and projects; and explains the boolean flags' install side effects.

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 is a 'First-run setup wizard' that 'Generates ~/.sassymcp/persona.md from your answers.' This gives a specific verb, resource, and output, and distinguishes it from sibling setup-related tools by naming the exact file it produces.

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?

It provides clear context: 'Call with your profile to personalize SassyMCP. All fields optional.' This tells the agent when to use the tool. It does not explicitly list when not to use it or name alternatives, but the first-run framing and optional-field guidance are sufficient.

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