hubspot_workflows_get

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

Discloses BETA status, OAuth scope requirement, and that it returns the full flow definition. As a read operation with no annotations, this is adequate, though rate limits or error handling are not mentioned.

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?

Two sentences, no filler. Each sentence adds distinct information: action+API in first, return+auth in second. Front-loaded with the core purpose.

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 one required parameter, no output schema, and simple GET behavior, the description covers essential aspects: what it does, how to call it, what it returns, and authorization. No gaps for an agent to invoke correctly.

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 100% with a clear description of flowId. The description reinforces the parameter's purpose (by its ID) and source (v4 API), adding value beyond the schema alone.

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?

Clearly states it gets a single automation workflow by ID from HubSpot Automation v4 API, specifying the return content and required OAuth scope. Distinguishes from siblings like list and v3_get through API version and singular retrieval.

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?

Describes when to use (when you have a specific flow ID) but does not explicitly mention when not to use or provide alternatives. The BETA tag and API version hint at context, but no direct comparison to siblings.

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