hubspot_workflows_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It notes the BETA status, required OAuth scope, and that complex fields require external documentation. However, it does not describe what the tool returns after creation, whether it is idempotent, or what errors might occur. This is a moderate gap for a mutation tool.

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 concise with four sentences. The first sentence states the core purpose, the second clarifies required vs optional fields, the third warns about complex schema, and the fourth notes OAuth scope. No superfluous content, and it is front-loaded.

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 7 parameters with 100% schema coverage and no output schema, the description covers creation intent, required fields, optional field deferral, external references for complex schemas, and auth. It lacks explicit mention of return value or error behavior, but overall it is fairly complete for a create tool.

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 100%, so baselines at 3. The description adds value by emphasizing required fields, providing a practical usage hint for the 'type' enum (e.g., CONTACT_FLOW is most common), and warning about complex recursion in enrollmentCriteria. This extra context raises the score above baseline.

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 it creates an automation workflow in HubSpot Automation v4 API, using the verb 'Create' and specifying the resource. It mentions the BETA status and references the update sibling tool for post-creation configuration, but does not explicitly distinguish from other sibling tools like list or get.

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 identifies when to use this tool (to create a workflow), notes the required fields, and points to hubspot_workflows_update for subsequent configuration. It also mentions the required OAuth scope. However, it does not provide explicit 'when not to use' guidance or compare to other create tools for different objects.

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