list_chatflows

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

With no annotations, the description carries the full burden. It describes the return format (IDs, names, metadata) and scopes to 'all', implying a read-only operation. This is transparent enough for a simple list tool, though it could mention any pagination or absence of filtering.

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 two short sentences that each add necessary information: what the tool does and what it returns. No waste, no repetition, and front-loaded with the 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?

For a zero-parameter list tool with no output schema or annotations, this description covers the essential aspects: the action, the resource, and the returned fields. Minor gaps like possible response size or ordering do not significantly reduce completeness.

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?

There are zero parameters, so the baseline of 4 applies per the rubric. The description adds no parameter-specific detail, and none is needed given the zero-parameter 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' with a clear resource ('chatflows') and scope ('all'), making it immediately distinguishable from sibling tools like get_chatflow. It also states the returned data (IDs, names, metadata), which fully clarifies the tool's purpose.

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 phrase 'List all chatflows' clearly implies use when the agent needs the complete set, as opposed to get_chatflow for an individual item. However, it does not explicitly mention alternatives or when-not-to-use, so it does not fully meet the 5-level criterion.

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