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

Annotations already disclose readOnlyHint=true and destructiveHint=false, so the read-only nature is established. The description adds useful behavioral context by specifying result contents ('conditions and action') and ordering ('newest priority first'), which goes beyond the structured 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?

Two sentences, no filler. The first sentence states the operation and key output traits, and the second gives concrete use cases. Every clause 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 provides the core output expectations and ordering, and the input schema covers the parameters thoroughly. Since there is no output schema, a little more detail about the returned rule shape could help, but the description is sufficient for correct invocation.

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% for both parameters, including the householdId guidance to call list_households. The tool description does not add parameter-level detail, but the schema fully covers it, so the baseline score of 3 is appropriate.

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?

States a specific verb and resource: 'List the household automation rules with their conditions and action.' It also adds a sort-order detail, 'newest priority first,' which distinguishes it from generic listing tools and clarifies what the result contains. Sibling tools like preview_rule or list_transactions are clearly different in scope.

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 usage contexts: 'before answering "what rules do I have" or before creating one that may already exist.' This clearly signals when the tool should be used, though it does not discuss exclusions or compare directly to sibling alternatives beyond those use cases.

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