apex_generate_wizard

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

All annotations are false/non-indicative, so the description must carry the burden of behavioral disclosure. It reveals the generated artifact (wizard with steps, progress bar, navigation) but does not disclose side effects, such as page creation/overwriting behavior, permissions required, or consequences of using existing page IDs. This is a significant gap for a 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?

The description is a single, front-loaded sentence with no filler. It packs the verb, object, scope, and key features efficiently, earning its place with every word.

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 combination of full parameter schema coverage, an output schema, and the concise description covers the basic invocation needs. However, important contextual elements—side effects, prerequisites, and alternatives—are missing, leaving the agent with only partial information for safe and confident use. For a mutating generation tool, this is adequate but not complete.

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?

The schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds a useful hard constraint—'2-6 steps'—which is not present in the schema, helping the agent validate input. It does not add detail for other parameters, but the schema descriptions are already sufficient.

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 uses a specific verb ('Generate') and identifies the exact resource ('multi-step wizard') with key characteristics (2-6 steps, progress bar, items, navigation buttons). This clearly distinguishes it from sibling tools like apex_generate_dashboard or apex_add_progress_tracker, and the scope is explicit.

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 implies when to use the tool: when a multi-step wizard is needed. However, it provides no explicit guidance on when not to use it or which alternative tools to prefer, such as simpler form generators or single-step page builders. The 2-6 step constraint offers some context but no explicit exclusions.

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