hubspot_workflows_v3_get

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

No annotations exist, but the description only notes it's a legacy GET. It does not disclose authentication needs, error conditions, or response format. For a simple read tool, more context is expected.

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: one for purpose, one for usage guidance. No fluff, front-loaded with key information.

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 simple one-parameter GET with no output schema, the description adequately covers purpose and usage. Missing a brief note on return value but still complete enough for selection.

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 single well-described integer parameter. Description adds legacy context but no additional parameter meaning beyond schema. Baseline 3 is appropriate.

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?

Description clearly states 'Get a single Workflow by ID using the HubSpot Automation v3 API'. Verb and resource are specific, and the legacy API note distinguishes it from v4 versions and sibling tools like hubspot_workflows_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?

Explicitly advises against using for new integrations ('prefer Automation v4 flows for new integrations'), providing clear when-to-use context and an alternative.

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