List tunnels with optional size and starting index pagination to fetch specific pages of results.
List tunnels with optional spec.size/spec.from pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| spec.from | No | Starting index for pagination (zero-based). | |
| spec.size | No | Max results per page. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must convey behavioral traits. It mentions pagination but does not disclose whether the operation is read-only, what happens without parameters, or any side effects. The description is insufficient given the lack of annotations.
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 and front-loaded. Every word serves a purpose with no redundancy.
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 list operation with two parameters and no output schema, the description is adequate but leaves ambiguity about default behavior (e.g., returns all tunnels if no pagination). It could be more complete by clarifying the default response.
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 coverage is 100% with descriptions for both parameters. The description adds marginal value by linking them to pagination, but does not provide additional context beyond the 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 clearly states the tool lists tunnels and supports pagination with spec.size/spec.from. It is specific about the action and resource. However, it does not explicitly distinguish this from the sibling tool sdcloud_get_tunnel, though the pagination hint provides some differentiation.
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 provided on when to use this tool vs. alternatives like sdcloud_get_tunnel. There is no mention of prerequisites, scope, or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.