compose_business_workflow

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

With no annotations, the description carries full behavioral burden and does well: it discloses hidden setup (webhooks, polling watchers, state transitions, idempotency, retries, approval gates) and the governance rule that publish=true is rejected until a client call. This tells the agent the tool creates governed drafts only, not executed/published workflows.

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?

Four sentences, all functional: definition, use-case, hidden-setup explanation, and governance constraint. Front-loaded with the action; no filler.

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?

The description covers purpose, triggering situation, hidden technical details, and governance, which is strong for a complex builder. However, with 10 parameters and no annotation support, the lack of any concrete parameter guidance (especially the required objective and how to supply primitive_ids) keeps it from being fully complete.

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 coverage is 0% and parameter descriptions are absent. The description only hints at publish (explicitly) and loop/primitives loosely; it does not clarify objective, inputs, owner_role, workflow_name, trigger_event, or max_iterations. This leaves an agent guessing on most of the 10 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 opens with a specific verb+resource: 'Draft an Agent Builder workflow from business primitives.' Unlike siblings like compile/validate/simulate, 'Draft' positions it as the creation step, and the scope ('from business primitives') differentiates it from more general authoring tools like author_agentic_workflow or dynamic_workflow_start.

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?

It explicitly states when to use: 'when the user wants an operational workflow or Agentic loop made out of primitives.' It also provides a usage constraint with 'rejects publish=true before any client call.' It does not name alternatives or state when not to use, so not a 5.

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