hubspot_enrollment_get_enrollments

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

No annotations are provided, so the description must carry the full burden. It states the tool returns a list of workflows the contact is currently enrolled in, but does not disclose any behavioral traits such as side effects, rate limits, or permission requirements. For a read operation, this is minimal but acceptable.

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 two sentences long, front-loads the action and resource, and contains no redundant information. Every word adds value.

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 the simple structure (single required parameter, no output schema), the description adequately explains what the tool does and returns. It could mention that results are limited to active enrollments, but it already says 'active'. Minor improvement possible but overall complete for its 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?

There is one parameter (vid) with 100% schema description coverage. The tool description adds 'HubSpot VID (contact record ID)' which matches the schema's description. Since the schema already documents the parameter, the description adds no extra value beyond confirming the context.

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 uses a specific verb ('Get') and resource ('active workflow enrollments for a contact by HubSpot VID'), clearly distinguishing it from siblings like hubspot_enrollment_enroll (enroll) and hubspot_workflows_list (list all workflows). It precisely states the action and the 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 clearly indicates when to use the tool (to retrieve enrollments for a specific contact). It does not provide explicit when-not-to-use or alternatives, but the context is clear enough given the sibling tools that perform different enrollment actions.

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