hubspot_workflows_v3_list

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

No annotations are provided, so the description must carry the full behavioral burden. It only states it returns a flat list of workflow definitions, but does not disclose that it's read-only, safe to call, or details about pagination, authentication needs, or any side effects. The lack of behavioral context is a significant gap for a tool with zero annotation coverage.

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 extremely concise with two sentences that efficiently convey the tool's purpose, legacy status, and return format. Every sentence adds value without any 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?

For a list tool with two parameters and no output schema, the description provides the basic purpose and return format ('flat list of workflow definitions'). However, it omits details about pagination behavior, ordering, and what the definitions contain. The information is adequate but not fully complete for an agent to understand all aspects of the 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 the schema already documents both parameters (limit and offset) with descriptions. The tool description does not add any additional meaning or context beyond what the schema provides, meeting the baseline expectation.

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 lists all workflows using the HubSpot Automation v3 API, with a specific verb ('List') and resource ('Workflows'). The '[LEGACY]' prefix distinguishes it from potential v4 alternatives, and it explicitly notes it's the legacy API, helping the agent differentiate it from sibling tools.

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 advises to prefer Automation v4 flows for new integrations, providing explicit when-to-use and when-not-to-use guidance. While it doesn't name the exact alternative tool, it gives clear context to avoid using this v3 API for new work.

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