enable_valet_mode

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

The description discloses one behavioral trait: 'auto-wakes if asleep', which provides useful context. However, with no annotations, it does not cover other important aspects such as idempotency, prerequisites, or side effects, so transparency is partial.

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 that conveys the core action and the auto-wake behavior without waste. It is highly concise and well-structured.

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 tool is relatively simple, and the description covers the main action and a key behavior. However, it does not explain what valet mode affects, nor does it mention expected outcomes or error cases, making it minimally complete but not rich.

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 input schema has 100% coverage with descriptions for all three parameters, so the schema does the heavy lifting. The tool description adds no additional detail about parameters, keeping this at the baseline score.

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+resource ('Enables Valet Mode') and clearly identifies the action. It also adds a behavioral detail ('auto-wakes if asleep'), which distinguishes it from sibling tools like disable_valet_mode or enable_guest_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?

The description implies usage from the name and context, but offers no explicit guidance on when to use this tool versus alternatives (e.g., guest mode or sentry mode). There are no exclusions or alternative mentions, so it falls short of clear usage guidelines.

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