list_saved_workflows

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

With no annotations, the description carries the disclosure burden; it does say the tool reads a specific directory and returns names and paths, which conveys it is a benign read and hints at output shape. It omits what happens when the directory is empty or missing, whether paths are absolute or relative, and whether it recurses subdirectories.

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?

A single short sentence with no padding, and the return contents (names and paths) are front-loaded. It is perhaps slightly under-specified rather than overly long.

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 annotations or output schema, the description gives only a minimal sketch of the return value. It lacks the source specificity (absolute vs relative paths, recursion, ordering) or follow-up guidance an agent would need to use the results reliably.

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 takes zero parameters, so the baseline of 4 applies. The description correctly indicates nothing needs to be supplied and no filtering options exist.

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 states a specific verb and resource (list saved workflows) and specifies the source location (workflows/ directory). It implicitly distinguishes from list_templates by scoping to saved workflows, but never names the sibling tools it is not (e.g., load_workflow) or what 'saved' means precisely.

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?

Usage is only implied: an agent can infer this is the way to discover existing workflows before loading or building one. There is no explicit when-to-use, no mention of load_workflow as the follow-up, and no statement about when this is preferable to list_templates.

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