workflow_add_conditions

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it generates conditional branching logic and mentions 'Pro feature', but it does not describe side effects, whether it writes to a project, what happens to existing workflows, or how the api_key parameter is used.

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 short and front-loaded, but it is under-specified rather than efficiently complete. It omits essential usage context and parameter meaning, so the brevity does not serve the agent's decision-making.

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 two parameters, no output schema, and no annotations, the description gives only a high-level intent plus a feature flag. It does not explain the expected input, the result format, or how this fits into a workflow project, leaving significant gaps for correct invocation.

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 only 50%, with 'api_key' undocumented in the schema and no mention in the tool description. The description does not clarify how 'directory' relates to the generated branching logic or what 'api_key' is for, failing to compensate for the schema's gaps.

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 identifies the action ('Generate') and the resource ('conditional branching logic'), and the tool name adds context that this applies to workflows. However, it does not explicitly differentiate from sibling tools like workflow_add_steps or workflow_generate_engine, leaving some ambiguity about how 'conditions' differs from 'steps'.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no context about whether it modifies an existing workflow or creates a new one. The 'Pro feature' note hints at a licensing requirement but does not explain practical usage conditions.

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