hubspot_create_workflow

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

Annotations already declare the tool is non-read-only and destructive, so the description's additional routing and auth-scope context (domain-agent dispatcher, JWT, tenant, company) adds some value. However, it does not disclose what the create action actually changes in HubSpot, whether repeated calls can create duplicates, or how success is surfaced.

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, front-loaded with the primary action, and uses a clean Args block. The routing/scope sentence adds useful context without bloating the text.

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 destructive create action with two unconstrained optional parameters and no schema-level descriptions, the definition is too thin: it does not explain what workflow creation entails, whether a message alone is sufficient, or how an agent should verify the result via siblings like hubspot_get_workflow or hubspot_list_workflows.

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?

With 0% schema description coverage, the description carries the parameter-semantics burden. It adds meaning by explaining `message` as a free-text objective and `inputs` as an optional JSON string, which goes beyond the bare schema, but it gives no domain-specific structure, examples, or expected keys for the inputs.

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 clear directive—'Run the hubspot domain agent action `create_workflow`'—so an agent can tell this is the invocation point for the create-workflow capability and can distinguish it from siblings like hubspot_get_workflow or hubspot_create_campaign. It stops short of stating the actual outcome (a new HubSpot workflow is created), so it leans partly on the tool name.

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?

No guidance is provided on when to choose this tool over alternatives such as hubspot_get_workflow, hubspot_update_workflow, hubspot_list_workflows, or other hubspot_create_* tools. The description only explains routing mechanics, not selection criteria or prerequisites.

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