execute_scene

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'execute' which implies a mutation, but it does not mention side effects, error behavior, authentication needs, or whether the operation is reversible. The example with a Japanese scene name adds little behavioral context.

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 two sentences plus an inline example, which is concise and front-loaded. Every word adds value, and the example is practical without adding clutter.

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?

For a simple tool with one parameter and no output schema, the description gives required usage context (check list_scenes first). However, it doesn't mention what happens after execution (e.g., success/failure output) or any side effects, which is a gap given no annotations.

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 schema already provides 100% coverage for sceneName with a description in Japanese. The tool description adds the phrase 'by name' and an example, but these do not significantly enhance understanding beyond the schema. Baseline of 3 applies due to high schema coverage.

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 'Execute a SwitchBot scene by name,' using a specific verb (execute) and resource (scene). It is distinct from siblings like list_scenes (which lists scenes) and control_device (which controls devices).

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 explicitly instructs to use list_scenes first, which provides clear usage context and a sibling alternative. It doesn't specify when not to use it, but the guidance is sufficient for the tool's simple purpose.

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