create_workflow

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds the admin-permission requirement and the queue-binding semantics, which is real added context. It does not describe what happens on conflict or whether the created entity can be re-created, so it is adequate but not rich.

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?

Three compact clauses with no wasted words, and the core action plus the key queue caveat are front-loaded. It is efficient, though the parenthetical "(admin)" is slightly cryptic and the sentences truncate some detail.

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 7-parameter nested create tool with no output schema, the description covers the sharing nuance and issue-type attachment but leaves the required steps/initialAction structure entirely to the schema. Given the nested-object complexity, a bit more on what a valid workflow requires would round it out.

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 description coverage is 71%, so the schema carries most parameter meaning. The description adds value for two parameters — the omit-queue-to-share convention and that issueTypeResolutions is how issue types get attached — but says nothing about the required steps, initialAction, or type beyond what the schema states. Baseline 3 fits.

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?

States a specific verb and resource ("Create a workflow") and enumerates the substance it holds (statuses/steps plus transitions), so the agent knows this builds a workflow object rather than reading or editing one. It stops short of differentiating from siblings like update_workflow or get_workflow, which is what a 5 would require.

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?

It gives one conditional usage rule — "Omit 'queue' to create a common workflow available to all queues" — which is genuinely useful branching guidance. However, it never says when to reach for create_workflow versus update_workflow, nor outlines prerequisites beyond the parenthetical "(admin)".

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