List available Maestro flows

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds the key behavioral trait that the tool works without Maestro installed, and explains the return values. It does not contradict annotations.

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 sentences long, with the first sentence covering the core functionality and the second adding usage guidance. Every word is informative with no 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?

For a zero-parameter tool with no output schema, the description is fairly complete: it states what files are listed, what is returned, and when to use it. It doesn't explain what DEVILGE_FLOWS_ROOT is, but that is likely environment-specific knowledge.

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, so the description cannot add parameter meaning. The baseline for zero parameters is 4. The description does add context about what the tool returns, which is relevant but not parameter-related.

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 specifies the action 'Lists every *.yaml/*.yml flow file', the resource 'under DEVILGE_FLOWS_ROOT', and the returned fields (name, relative path, size, 5-line preview). It also distinguishes from sibling tools by noting it works without Maestro installed.

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 suggests using this tool to discover existing flows before deciding to install Maestro, providing clear usage context. However, it does not explicitly state when not to use it or mention alternative tools for similar listing needs.

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