hubspot_enrollment_enroll

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

With no annotations provided, the description carries the full burden. It discloses the basic behavior (enrollment) and a prerequisite, but does not mention side effects, idempotency, error cases, or return values. It is adequate but not detailed.

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 (26 words), front-loaded with the main action, and contains no unnecessary words. Every sentence 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?

For a simple mutation tool with fully described parameters, the description covers the primary action, prerequisites, and input hints. It does not describe output, but given no output schema, this is acceptable. The tool fits well among siblings.

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%, so baseline is 3. The description restates the required parameters ('workflow's numeric ID and contact's email') but adds no new constraints or formatting beyond the schema, thus meeting but not exceeding the baseline.

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 the verb 'Enroll' and the resource 'a contact into a HubSpot Workflow (Automation v2)'. It distinguishes from siblings like hubspot_enrollment_unenroll by specifying the action direction, and includes prerequisites and input hints.

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 implies usage context by stating the prerequisite 'The contact must exist in HubSpot'. It does not explicitly mention when not to use or compare to alternatives like hubspot_enrollment_unenroll, but the context is clear enough for a simple action tool.

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