enableDemoMode

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the outcome ('consistent status bar indicators') but doesn't describe side effects, permissions needed, whether changes persist, or what happens if the tool fails. For a configuration tool with 8 parameters, this leaves significant behavioral gaps.

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, efficient sentence that front-loads the core purpose. Every word earns its place: 'Enable demo mode' states the action, 'with consistent status bar indicators' specifies the configuration aspect, and 'for screenshots' provides the use case context.

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 complexity (8 parameters, configuration operation) and absence of both annotations and output schema, the description is minimally adequate. It states what the tool does but lacks information about behavioral consequences, error conditions, or what success looks like. The 100% schema coverage helps but doesn't compensate for missing behavioral context.

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 the schema already documents all 8 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (like explaining relationships between parameters or providing usage examples). Baseline 3 is appropriate when schema does all the work.

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 action ('Enable demo mode') and the purpose ('with consistent status bar indicators for screenshots'), distinguishing it from sibling tools like 'disableDemoMode' by specifying its enabling function. It's specific about the resource being manipulated (demo mode configuration).

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 usage context (for screenshots) but doesn't explicitly state when to use this tool versus alternatives like 'setDeviceMode' or 'disableDemoMode'. No prerequisites or exclusions are mentioned, leaving the agent to infer appropriate usage scenarios.

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