Run a Maestro flow (optional)

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

Annotations are basic (readOnlyHint false, etc.), but the description adds significant behavioral context: Maestro is optional and returns MAESTRO_NOT_INSTALLED with install command, runScript blocks are denied by default (with env var to allow), MAESTRO_DISABLE_ANALYTICS is always injected, and params are injected as -e KEY=VALUE.

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 five sentences, front-loaded with the main action, and each sentence adds unique information. No redundant or unnecessary text.

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?

No output schema, so the description covers return value for the not-installed case but does not detail the success output (likely Maestro's stdout). Given the complexity of the tool (external process execution), the description is mostly complete but could mention the standard output format.

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?

Schema coverage is 100% (both parameters described), so baseline is 3. The description adds value by explaining that 'name' is a basename without .yaml extension and lives under DEVILGE_FLOWS_ROOT, and that 'params' are injected as -e KEY=VALUE. This provides meaningful context beyond the schema's generic descriptions.

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 clearly states it executes a Maestro YAML flow, using a specific verb and resource. It distinguishes from sibling tools like devilge_list_maestro_flows (listing) and devilge_validate_maestro_flow (validation) by explicitly saying 'Executes'.

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 implicitly says when to use (to run a flow) and provides context like the optional nature of Maestro and the install command if missing. However, it does not explicitly exclude other sibling tools or provide alternative guidance.

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