shelly_webhook_list

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

Annotations already declare readOnlyHint=true, so the read-only behavior is disclosed. The description adds 'Local-only', which provides additional context about scope. However, it does not disclose potential errors, rate limits, or authentication requirements, which would be valuable for a read operation.

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 extremely concise (two short sentences) and front-loads the primary purpose. However, it sacrifices necessary detail, particularly about the parameter, which might require more space.

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 the tool is a simple read-only list operation with one parameter and an output schema exists (not shown), the description provides the core purpose but lacks explanation of output format, pagination, or error scenarios. It is minimally adequate for simple usage.

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 schema has 1 parameter ('device') with 0% coverage (no description in schema). The description mentions 'on a device' but does not clarify what format or identifier the 'device' parameter expects (e.g., ID, name, IP). This leaves ambiguity for the agent.

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 action ('List') and the resource ('webhooks configured on a device'). It also adds a scope qualifier ('Local-only'), which distinguishes it from potential cloud-based operations. The tool name and action are 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 provides no guidance on when to use this tool versus its siblings (e.g., shelly_webhook_create, shelly_webhook_delete) or any context about prerequisites. It does not mention alternatives or when not to use it.

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