smarthome_command_plan

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

With no annotations provided, the description bears full burden for behavioral disclosure. It only states it runs a domain agent action and routes through dispatcher, but omits side effects, idempotency, rate limits, or any consequences of invocation. The presence of an output schema is not leveraged in the description.

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 extremely concise: three sentences front-loading the purpose, followed by a structured list of arguments. No extraneous information; every sentence earns its place.

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 absence of annotations and output schema documentation, the description is marginally adequate. It explains what the tool does and its auth scope, but omits return value, error scenarios, and prerequisites. For a simple two-parameter tool, it feels partially complete.

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 parameter description coverage is 0%, so the description must compensate. It adds that 'message' is a free-text objective and 'inputs' is an optional JSON string, which clarifies usage beyond the bare schema. However, it lacks formatting examples or constraints (e.g., valid JSON structure).

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 'Run the smarthome domain agent action `command_plan`', which specifies a verb and resource. However, it does not differentiate from sibling smarthome tools like 'smarthome_scene_assist' or 'smarthome_automation_review', leaving ambiguity about when to use this specific action.

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 mentions routing through the dispatcher under JWT/tenant/company scope, which provides context but no explicit guidance on when to use this tool versus alternatives. No when-not-to-use or alternative tool mentions are provided.

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