create_workflow

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

The description states 'Create', implying a write operation, but no annotations exist to confirm behavior. It fails to disclose important traits such as whether the tool is idempotent, what happens on duplicate creation, or if it triggers side effects.

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 a single sentence, which is concise. However, it is under-specified rather than efficiently 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 the vague schema (one undocumented generic param) and no annotations, the description is completely inadequate. It does not explain the return value, error conditions, or relationship to sibling tools. Even with an output schema, the input is underspecified.

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?

The single parameter 'params' is a loosely typed anyOf (object or null) with no description in the schema (0% coverage). The tool description adds no semantics about what keys or values are expected, making it unusable without external knowledge.

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 'Create a workflow record' is a tautology that restates the tool name without adding specificity. It does not clarify what 'workflow record' means, what type of workflow, or how this differs from siblings like submit_workflow_input.

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 is provided on when to use this tool versus alternatives such as submit_workflow_input, confirm_workflow, or get_workflow. There is no mention of prerequisites, context, or exclusions.

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