list_scenes

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

No annotations are provided, so the description carries the full burden. It discloses caching behavior via the 'refresh' parameter, but does not state if the operation is read-only, requires authentication, or has rate limits. The read-only nature is implied by 'list', but not explicit.

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 very concise: one line for purpose and bullet points for arguments. No unnecessary information, each 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?

The description lacks details about the return format. With no output schema, the agent does not know what fields are returned (e.g., scene ID, name, state). This is a gap given the context of sibling tools like run_scene that likely need scene IDs.

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 add meaning. It provides Chinese explanations for both parameters: '按家庭ID过滤' (filter by home ID) and '是否强制刷新缓存' (whether to force refresh cache), which adds value beyond the schema's type and default.

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 '列出所有米家场景' (List all Mi Home scenes), which is a specific verb and resource. It distinguishes from sibling tools like run_scene, which executes a scene.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical workflows, or conditions that would favor this tool over others like list_devices or get_device.

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