create_workflow

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

Without annotations, the description carries the full burden. It mentions a side effect (saving to a file path) but does not disclose whether existing workflows with the same name are overwritten, error conditions, permission needs, or any other behavioral traits of the mutation.

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 that is front-loaded with the action and resource. No redundant words, and it efficiently conveys the core purpose and a key detail (storage path).

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 simple create tool with two parameters and an output schema (not shown), the description is minimally adequate. It states the input (YAML content) and output location, but lacks details on validation, errors, and answer format. The output schema may cover returns, but the description still feels incomplete.

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 description does not add meaning beyond the schema's field names and types. It hints that 'content' should be YAML but does not explain required format, constraints, or how to use the 'name' parameter. With 0% schema description coverage, the description fails to compensate.

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 the action (create), the resource (a new user workflow), and the source (YAML content). It distinguishes itself from siblings like delete, get, list, and update by specifying creation. The storage location is mentioned, adding context. However, it could be more explicit about the YAML format.

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?

The description does not provide any guidance on when to use this tool versus alternatives like 'update_workflow', 'delete_workflow', or other tools. No prerequisites, caveats, or when-not-to-use scenarios are mentioned.

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