hubspot_automation_callback_complete

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

With no annotations provided, the description must fully disclose behavior. It effectively explains the effects of each hs_execution_state value (continue, continue despite failure, stop enrollment). It does not cover authentication, rate limits, or idempotency, but for a simple callback completion this is adequate.

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?

Three short, well-front-loaded sentences: purpose, timing, and execution state options. Every sentence earns its place with no redundancy or fluff.

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 two parameters (one nested) and no output schema, the description covers the essential purpose and behavior. It could mention that no output is returned or that the workflow continues based on the state, but it is sufficiently complete for this tool's complexity.

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?

The schema already describes both parameters. The description adds value by explaining the practical meaning of the hs_execution_state enum values (SUCCESS continues, FAIL_CONTINUE continues despite failure, BLOCK stops enrollment). This goes beyond the schema's brief description.

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 identifies the verb 'complete' and resource 'async custom-action callback' within HubSpot Workflows. It specifies the version (v4 automation runtime). However, it does not explicitly differentiate this single-callback tool from its batch counterpart among siblings, reducing clarity of scope.

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 states when to call ('after your external action finishes') and explains the three possible states. However, it provides no guidance on when not to use this tool, no mention of prerequisites (e.g., having a valid callbackId), and no comparison with the sibling batch tool for multiple callbacks.

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