smarthome_scene_assist

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

The annotations already signal destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds JWT/tenant/company scope and dispatcher routing, but does not disclose what scene_assist actually does, what side effects may occur, or what 'destructive' behavior to expect. It adds minimal behavioral value beyond the annotations.

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 short and front-loaded with the primary purpose, followed by concise routing context and a clean Args block. Every sentence earns its place, though more behavioral detail could be added without bloating it.

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?

An output schema exists, so return-value documentation is not needed, but the description still does not explain what the scene_assist action accomplishes, what constitutes a valid message or inputs, or when this is preferable to the many smarthome sibling tools. For an agent to confidently invoke it, the core domain behavior is missing.

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 0%, so the description must compensate. It does define message as 'Free-text objective' and inputs as 'Optional JSON string of structured inputs', which adds meaning beyond the schema's bare titles and defaults. However, the semantics are shallow and do not explain expected structure or examples.

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 states a specific verb ('Run') and resource ('smarthome domain agent action scene_assist'), and adds that it routes through the domain-agent dispatcher. It is clear about what the tool executes, though it does not explicitly distinguish it from sibling smarthome tools or dispatch_domain_agent.

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?

No guidance is provided about when to use this tool versus alternatives such as smarthome_chat, smarthome_command_plan, or dispatch_domain_agent. The routing and scope details explain how it executes, but not when an agent should select it.

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