compile_business_workflow

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

The description adds substantial behavioral context beyond the annotations: 'no network calls', 'SDK is the source of truth', and a detailed enumeration of what the emitted definition contains (tenant/company/RBAC policy, approval gates, hidden setup, state transitions, recovery, test plan). These details meaningfully enrich the readOnlyHint and idempotentHint already declared.

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 tightly packed sentences, each earning its place: the main verb-resource statement is front-loaded, followed by trust/safety context and an output-content summary. No filler or repetition of schema details.

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?

An output schema exists and the description usefully previews the emitted artifact's contents, so return-value coverage is adequate. The remaining gaps are the 9 parameters with no schema descriptions and no explicit differentiation from compose_business_workflow, which leaves the agent short of confidently invoking the tool correctly on the first try.

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% across 9 parameters, and the description barely compensates: it gestures at the source primitives (implying primitive_ids) but never explains objective, loop, inputs, owner_role, trigger_event, workflow_name, workflow_type, or max_iterations. With low schema coverage, the description carries the burden of explaining parameters and largely fails to do so.

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 verb and resource: 'Compile a portable workflow draft from Lightbulb business primitives.' This clearly distinguishes it as a draft-producing tool rather than an execution, validation, or simulation tool among the workflow siblings. However, it never explicitly differentiates from the near-sibling 'compose_business_workflow', so the separation is clear in substance but not in explicit contrast.

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 clear usage context: this is a safe, local compile step ('performs no network calls and no writes') that emits an inspectable definition, implying it should be used when an agent wants to materialize and review a workflow draft before execution. It does not name alternatives or give when-not-to-use conditions, so it stops short of the top score.

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