list_tunnels

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

No annotations are provided, so the description carres the full burden of behavioral disclosure. It conveys only that this is a listing operation, with no mention of pagination, response contents, whether all tunnel states are included, or account-scoping semantics — all relevant behaviors for a list endpoint.

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?

One short front-loaded sentence with zero filler; every word earns its place and the verb leads. It loses a point only because the brevity leaves usage and behavioral context unstated, though those gaps are penalized in their own dimensions.

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?

Adequate to invoke correctly: one required, fully documented parameter and a single clear operation. However, with no annotations and no output schema, the description omits pagination and return-shape details that an agent enumerating a large tunnel inventory would reasonably need.

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%; account_id is already documented as 'The account ID'. The phrase 'in an account' loosely corroborates the parameter's role but adds no format, default, or scope detail beyond the schema, so the baseline 3 applies.

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 states a specific verb ('List') and resource ('Cloudflare Tunnels') with account scoping, making the tool's function unmistakable. It differntiates inherently from get_tunnel (singular fetch) and get_tunnel_configuration (config read), though it never explicitly disambiguates from list_magic_transit_ipsec_tunels/ list_magic_transit_gre_tunels, which are a different tunnel product family.

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 on when to choose this over get_tunnel, list_tunnel_connections, get_tunnel_configuration, or the Magic Transit tunnel listings. The text only says what the tool does; when-to-use and when-not-to-use are left entirely to inference from the tool name.

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