start_onboarding

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds behavioral context: it shows disclosures and returns text plus an acknowledgment string. No contradiction exists. The description enhances understanding beyond annotations.

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 three sentences with no wasted words. It front-loads the main action ('Begin the AlgoChains setup wizard') and adds essential details (disclosures, ordering, return). Every 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 input schema and no output schema, the description sufficiently explains what the tool does and returns (disclosure text and acknowledgment string). It also provides ordering context. However, it could mention how the acknowledgment string should be used subsequently, but this is not critical.

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 tool has no parameters (0 params, 100% schema coverage). With zero parameters, the description need not explain parameter usage. Baseline is 4, and the description does not introduce any confusion.

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's purpose: 'Begin the AlgoChains setup wizard' with specific actions (show risk disclosure, privacy notice, compliance acknowledgment). It distinguishes from siblings by noting it 'MUST be called first by new users before connecting any broker' and mentions its return value.

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 states when to use: 'MUST be called first by new users before connecting any broker.' This provides clear context. However, it does not explicitly mention when not to use or list alternative tools, though siblings like accept_subscriber_terms or acknowledge_risk_disclosure are implied.

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