exit_demo_mode

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description reinforces these (stateless/read-only, does not change demo state) and adds behavioral context: response is verbose, presumes intent, and agent should not call as probe. No contradictions.

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?

Well-structured with clear sections and bullet-like flow. However, it is somewhat verbose with some repetition (e.g., 'stateless / read-only' appears twice). Still, every sentence adds value and it's appropriately detailed for a complex tool.

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?

Despite no output schema, the description fully explains return value (tailored decision tree, no-op outside demo mode). Covers all parameters with usage context, preconditions, agent behavior, and edge cases. Nothing missing for effective use.

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%, but the description adds significant context: hasLedger controls deferral, hasRunSetup skips setup walkthrough, chains drives RPC key recommendations, acquireKeys affects recommendation tone. This goes well beyond the brief schema descriptions.

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 builds a step-by-step guide for exiting demo mode. It specifies the output is a tailored decision tree, distinguishes itself from other tools by being stateless/read-only, and the sibling list contains no similar tools.

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 call (only after user confirmation of intent), provides pre-call questions (hasLedger, hasRunSetup, chains, acquireKeys), and when not to call (as a probe). Also covers edge cases: deferral if no Ledger, no-op outside demo mode.

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