exit_exhibition_mode

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

No annotations provided, so description carries full burden. It details password comparison tolerance, that it's a casual demo guard not real auth, success effects (restores speeds, reverse, power, DCC address), and failure behavior (leaves mode ON, returns instruction). Highly transparent.

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?

Description is well-structured with purpose first, then password details, then usage guidelines. However, it includes some redundancy (e.g., 'restoring full normal control' and later 'restores real speeds...'). Minor improvements could make it more concise.

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?

No output schema, but description hints at return behavior (instruction on failure). Covers success and failure outcomes. Could mention side effects on other tools or state, but generally complete for a simple toggle tool.

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 coverage is 0%, so description must compensate. It extensively explains the password parameter: must match configured password, compared tolerantly, reason for tolerance (voice transcription), and ethical warnings. This adds immense value 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 explicitly states 'Turn OFF exhibition mode, restoring full normal control.' It clearly identifies the verb (exit) and resource (exhibition mode), and distinguishes itself from siblings like enter_exhibition_mode and get_exhibition_mode.

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?

Provides explicit when-to-call: only when user explicitly asks and provides password. Gives clear warnings: never guess or supply password yourself, never reveal password. Also instructs to ask user to retry on wrong password. This is exemplary usage guidance.

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