yaaif_ambient_workflow_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one meaningful behavior: omitting workflow_graph triggers seeding from the Agent Spec workflow_design segment under certain conditions. However, it does not disclose side effects, whether an existing workflow is overwritten, permission requirements, default values for enabled or requires_approval, or what the response contains, leaving significant behavioral gaps.

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 two sentences with no filler, and the core purpose is front-loaded in the first sentence. The second sentence earns its place by explaining the key optional behavior. It is concise, though the heavy use of domain-specific terms like 'Agent Spec workflow_design segment' makes it dense.

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 11 parameters, nested objects, no output schema, and no annotations, the description is not complete enough for an agent to invoke the tool confidently. It explains only the workflow_graph/spec_id seeding path and leaves required parameter semantics, policy/trigger_rules structure, defaults, and post-install behavior unexplained. The tool is more complex than the description accommodates.

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 0%, so the description must compensate for 11 undocumented parameters. It adds useful meaning for workflow_graph and spec_id by explaining the seeding relationship, and it indirectly references ambient_agent_id. But it leaves name, policy, enabled, slot_key, description, trigger_rules, requires_approval, and workflow_async_enabled without any semantic guidance, which is a substantial gap for a tool with this many parameters.

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 states a specific action ('Install an ambient workflow graph') and a target ('under an ambient agent'), which clearly identifies this as a creation/installation tool. It is distinguishable from sibling tools like yaaif_ambient_workflow_get, yaaif_ambient_workflow_list, and yaaif_ambient_workflow_update by the verb 'install' and the notion of creating a graph. However, it relies somewhat on domain jargon ('ambient workflow graph') and does not explicitly contrast with the update sibling.

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 provides a clear usage condition for one parameter path: omit workflow_graph to seed from the Agent Spec workflow_design segment when spec_id or a bound ambient agent is available. This gives partial guidance on when to use the seeding behavior. It does not, however, say when to choose this tool over alternatives such as yaaif_ambient_workflow_update or yaaif_trigger_ambient_workflow, so the tool-selection guidance is mostly implied.

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