scene_activate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes a critical behavioral trait: that the operation is blocked without user confirmation. However, it doesn't mention other potential behavioral aspects like error conditions, response format, or side effects on other home automation systems.

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 perfectly concise with two sentences that each serve a distinct purpose: stating the action and stating the critical requirement. It's front-loaded with the core function and wastes no words while providing essential information.

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 2-parameter tool with no annotations and no output schema, the description provides good coverage of the activation behavior and confirmation requirement. However, it doesn't explain what 'activating a scene' actually does in Home Assistant context or what the expected outcome looks like, leaving some contextual gaps.

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 fully documents both parameters. The description adds no additional parameter semantics beyond what's in the schema descriptions, which already explain entity_id format and the required confirmation. This meets the baseline for 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 the specific action ('Activate a scene') and resource ('in Home Assistant'), distinguishing it from siblings like scene_create, scene_delete, or scene_list. It uses precise verb+resource language that leaves no ambiguity about the tool's function.

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 states when to use this tool ('REQUIRES user_confirmed=true - user must explicitly request scene activation'), providing clear prerequisites and conditions for invocation. This gives the agent concrete guidance on the mandatory confirmation requirement before using this tool.

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