list_channels

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

No annotations are provided, so the description carries the full burden. The verb 'List' implies a read-only operation, and 'authenticated agent' indicates authentication is required. However, it does not disclose details like pagination behavior, ordering, or whether any state is affected. For a simple listing tool this is adequate 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 a single, front-loaded sentence containing all essential information. Every word contributes to the purpose, and there is no redundancy or fluff.

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?

The core purpose is clearly stated, but the description is thin for a tool with no output schema and no annotations. It does not explain what a 'payment channel' entry looks like, what the limit parameter does, or how this relates to siblings like get_channel. Given the low complexity of the tool, this is a minimum viable description but leaves clear 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 input schema has a single optional 'limit' parameter with no description (schema coverage 0%). The description does not mention 'limit' at all, nor does it explain how results are paginated or capped. The meaning is inferable from the name and type, but the description fails to add any parameter semantics 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 uses a specific verb ('List') and a specific resource ('payment channels'), with a clear scope ('associated with the authenticated agent's wallet'). This clearly distinguishes it from sibling tools like get_channel (which fetches a single channel) and list_intents (which lists a different resource type).

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 does not explicitly state when to use this tool versus alternatives such as get_channel or get_history. There is no mention of 'use this to see all channels' or 'use get_channel for a single channel'. The context is implied but not stated.

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