onboarding_wizard

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 explains that each step returns instructions, code snippets, and progress, but does not disclose side effects, authentication needs, or behavior on error. For a wizard that likely creates data, persistence details are missing.

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 concise with a clear bullet list of actions, efficiently communicating the tool's purpose. It is front-loaded with the main function and avoids unnecessary details.

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 the tool's simplicity (no output schema, few parameters), the description covers basic operation but lacks information on error states, behavior when wizard has already been completed, or how to handle invalid action sequences.

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 100%, so baseline is 3. The description adds some value by listing actions and explaining return content, but largely echoes the schema enums. No additional detail on parameter format or constraints 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 it is an interactive setup wizard for new Prism users, listing specific actions and their purposes. It distinguishes itself from sibling tools, which are unrelated to onboarding.

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 implicitly suggests use for new users during setup but provides no explicit guidance on when to use this tool versus alternatives or when not to use it. Additional context about prerequisites or completion status would improve this dimension.

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