automations_get_scene_config

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

Discloses acceptance of two id formats and return of None on not found. No annotations provided, but description adequately covers behavior for a read operation. Could be more explicit about being read-only.

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?

Two sentences, no wasted words, front-loaded with purpose. Essential information efficiently conveyed.

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 output schema exists, description covers parameter format, return behavior, and what config contains (entities + states). Complete for a simple get tool.

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?

Adds value beyond schema by specifying accepted id formats (bare or prefixed). Schema coverage is 0% so description compensates well. Could include examples but sufficient.

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 verb 'Get' and resource 'scene's config dict', and distinguishes it from sibling tools like automations_list_scenes and automations_set_scene_config. It also specifies accepted id format.

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?

Provides explicit input format guidance ('bare id or scene.<id>') and return behavior (returns None if not found). Lacks when-not-to-use or explicit alternative selection, but implied sufficiently.

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