shelly_webhook_list

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds a real constraint not present in the schema or annotations — that the call is local-only (no cloud path) — which is valuable execution context, but it stops short of saying what happens if the device is unreachable or what the response contains.

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 short sentences, zero filler, with the core action stated first and the constraint appended. Nothing could be removed without losing content.

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?

An output schema exists, so return values need no explanation, and the tool is simple (one param, read-only). However, the identifier format for `device` and the practical meaning of "local-only" (LAN reachability, failure mode) are left unstated for an otherwise trivial 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?

Schema description coverage is 0% for the single required `device` parameter, and the description does not clarify whether it expects a device ID, name, or IP. The phrase "on a device" does little more than restate the parameter name, leaving the main invocation detail ambiguous.

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?

A specific verb+resource ("List webhooks configured on a device") that clearly contrasts with the create/update/delete webhook siblings without naming them. The distinguishing read-vs-write intent is obvious from the verb, though no sibling is explicitly named.

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?

"Local-only" implicitly tells the agent this only works when running against a device on the local network, but there is no explicit when-to-use guidance or mention of alternatives like querying config. Usage is inferable rather than stated.

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