List Lucky tunnels and WAF instances

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

The annotations already declare the operation safe: readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the domain context 'Cloudflared tunnels plus Coraza WAF instances' but reveals nothing about output shape, pagination, or whether WAF instances are nested or separate. This is acceptable but not rich.

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 exceptionally concise: one short phrase with no filler and the key resource types front-loaded. It loses a point for being a sentence fragment that lacks an explicit verb.

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?

There is no output schema, so the description should compensate by stating what is returned and in what form. 'Cloudflared tunnels plus Coraza WAF instances' conveys resource types but not whether results are merged, separate arrays, or paginated. For a simple zero-parameter read-only tool this is adequate but leaves real gaps.

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 tool has zero parameters and the schema has no properties, so there is nothing for the description to explain. Per the no-parameter baseline, a 4 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?

The title clearly states the action and resources: 'List Lucky tunnels and WAF instances', and the description pins down the exact types (Cloudflared tunnels, Coraza WAF instances). This distinguishes it from sibling list tools like lucky_list_wol_devices or lucky_list_ip_filters. However, the description itself is a noun phrase without an explicit verb, so purpose rests partly on the title.

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?

No guidance is given about when to use this tool instead of another list tool. With many lucky_list_* siblings, an agent receives no criteria or exclusions to help route correctly.

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