aap_launch_workflow

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

Annotations already mark readOnlyHint=false and destructiveHint=false, but the description adds a return format note (JSON with job id, status, monitoring tip), suggesting an asynchronous launch. However, it doesn't describe side effects, permission requirements, or that launching may trigger a job, leaving some behavioral gaps.

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 well-structured with an example, Args, and Returns sections. It is not overly verbose but includes some redundancy with schema descriptions and could be slightly tighter.

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 launch operation with a single nested params object, the description covers the action, all parameters, and return value. It lacks usage exclusions or prerequisites but is otherwise adequate for an agent to invoke correctly.

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?

Although schema coverage is listed as 0%, the description's Args section explicitly explains workflow_id, extra_vars, and limit, adding meaning beyond the schema. It also indicates optionality for extra_vars and limit, though it does not specify the JSON/YAML format for extra_vars that the schema includes.

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 'Launch an AAP workflow template' with a concrete example, making the verb and resource explicit. This distinguishes it from sibling tools like aap_launch_job_template by specifying the workflow template resource.

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 implies usage when you want to launch a workflow template but provides no explicit guidance on when to prefer this over aap_launch_job_template or aap_relaunch_job. No when-not-to-use or alternatives are mentioned.

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