Create a workflow

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

The description indicates a mutating operation and provides the API endpoint, but does not disclose behavioral traits like idempotency, error cases, or side effects. Annotations already show destructiveHint=false, but description adds minimal context beyond creation.

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 sentences, with first sentence redundant to title. Could be more concise by combining, but overall not overly verbose. Front-loading is acceptable.

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 tool with 7 parameters, nested objects, and no output schema, the description is insufficient. It does not explain return values, configuration details, or constraints, leaving gaps for the agent.

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 43% schema coverage, the description adds no additional meaning to parameters. It does not explain any parameter semantics beyond what is in the schema, missing an opportunity to clarify complex fields like buildConfig or envVars.

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 creates a new workflow service, specifying verb (create) and resource (workflow). It distinguishes from siblings like render_get_workflow or render_create_workflow_version.

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, prerequisites, or exclusions. There is no mention of when not to use it or comparison with similar creation tools.

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