list_workflows

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

The description provides no behavioral details beyond the implied read operation. With no annotations provided, the description carries the full burden of disclosure, but it fails to mention pagination, filtering, or output structure. The output schema exists but is not referenced.

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 short (two words), but this is under-specification rather than conciseness. While no information is wasted, the description fails to convey essential details.

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?

Given the presence of an output schema and 1 parameter with 0% coverage, the description is severely incomplete. It does not explain the output, parameter usage, or how this tool fits among 17 sibling tools. A complete description would include listing scope, filtering options, and relationship to get_workflow.

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 one parameter 'params' with no description coverage (0%). The description does not explain what this parameter does, its valid values, or its effect on the output. The parameter is a generic object allowing any properties, leaving the agent completely uninformed.

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 'List workflows' is a minimal statement that repeats the tool name without specifying scope, context, or differentiating features. It does not distinguish this tool from sibling tools like get_workflow or list_public_methods.

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 usage guidelines are provided. The description does not indicate when to use this tool, what parameters affect results, or how it compares to alternatives such as get_workflow or search-related tools.

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