workflow_create

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

Despite no annotations, description fully discloses behavior: returns run_id stored in sidecar, workers don't need it out-of-band, tags for filtering, status starts as 'created'. No contradictions.

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?

Five sentences, no fluff, front-loaded with purpose, each sentence adds value (usage, lifecycle, tags details). Extremely concise yet informative.

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?

Given many workflow siblings, description clearly differentiates this from workflow_discover and others. Covers lifecycle, sidecar integration, tags. Missing output schema details but mentions 'unique run_id'.

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?

With 0% schema coverage, description adds full meaning: name is required, tags are arbitrary key-value metadata for discovery filtering with examples (tags={'pipeline': 'data-etl', ...}).

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 states 'Register a new workflow and get back a unique run_id', which is a specific verb+resource+output. It distinguishes from siblings like workflow_discover by noting workers use discover to find it.

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?

Explicitly says 'Call this from the orchestrator before spawning workers' and explains that workers use workflow_discover instead. Provides lifecycle: created → claimed → running → done/failed.

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