list_chains

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

Although no annotations are provided, the description signals a read-only operation via 'List' and enumerates the return fields, giving a transparent view of expected output without hidden side effects.

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?

Single sentence, front-loaded with the action, then a compact enumeration of output fields. Zero wasted words.

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 description fully covers the tool's purpose and return value structure in the absence of an output schema. It explains what the user will receive, making it complete for a parameterless list operation.

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; the schema is empty with 100% coverage. The description need not add parameter details, so the baseline score of 4 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?

Clearly states 'List all task chains' – a specific verb+resource scope. Distinct from sibling list_workers and list_groups, and from chain mutation tools like create_chain or run_chain_now.

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 clearly implies the use case: to retrieve all task chains. It does not explicitly mention alternatives, but the context is unambiguous for a listing operation.

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