github_actions_create_workflow_dispatch

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

With no annotations, description carries full burden. It only states the action without disclosing side effects (e.g., triggers a run), required permissions, or potential errors. A mutation tool should at least indicate it initiates a workflow.

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?

Single sentence is concise but lacks detail. It is front-loaded with the verb, but the brevity sacrifices necessary context. Could be improved without being verbose.

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 and no annotations. Description fails to explain return value (likely the workflow run ID or nothing) or provide context about the body parameter (e.g., required fields like 'ref' and optional 'inputs'). Incomplete for a mutation tool with moderate complexity.

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% with basic descriptions for each parameter. The description adds no extra meaning beyond what the schema provides. Body parameter remains somewhat vague, but baseline 3 is appropriate given schema coverage.

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?

Description clearly states action 'Create a workflow dispatch event' with a verb and resource. It distinguishes itself from sibling tools like 'create_environment_variable' or 'approve_workflow_run'. However, it could be more explicit that it triggers a workflow run.

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 guidance on when to use this tool vs. alternatives. For example, it does not mention that this triggers a workflow_dispatch event, requiring the workflow to have that trigger. Sibling tools include many other action-related tools, but no differentiation.

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