list_outlets

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

No annotations are provided, so the description carries the full transparency burden. It clearly states the tool lists all outlets and discloses the exact return fields (id, name, room, on/off state, reachability), which is the core behavioral trait. While it does not mention error handling or empty results, the description adequately communicates the tool's read-only enumeration behavior.

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 two concise sentences, front-loaded with the core purpose ('List every outlet'). The second sentence provides return fields and usage guidance without redundancy. Every word earns its place, making this an exemplary concise description.

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?

For a simple zero-parameter list tool, the description is fully complete: it states scope, output fields, and how the ids integrate with sibling tools. The presence of an output schema reduces the need for detailed return descriptions, and the description provides enough context for an agent to invoke the tool correctly and use its results.

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?

The input schema is an empty object with zero parameters, so parameter semantics are fully covered by the schema. Per the rubric, 0 parameters earns a baseline of 4. The description adds context by confirming the tool lists all outlets without filters, which enriches the empty schema.

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 uses the specific verb 'List' and the resource 'outlets (smart plug) paired to the DIRIGERA hub', immediately establishing the tool's scope. The phrase 'every outlet' distinguishes it from sibling tools like get_outlet, set_outlet, toggle_outlet, and power_cycle, which operate on individual outlets. Purpose is unambiguous.

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 explicitly instructs 'Use the id with the other outlet tools', clearly positioning this tool as the enumeration/selection step before applying actions via siblings. This gives strong guidance on when to use the tool and how its output feeds into other operations, effectively distinguishing its role from the alternatives.

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