hubspot_quotes_assemble

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

No annotations provided, so description carries full burden. It discloses that the tool is a helper that performs a single operation with inline associations, default association type IDs, and overrides. It does not explicitly mention idempotency, error behavior, or return value, but covers essential behavioral aspects well.

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?

Approximately 4-5 sentences, front-loaded with main purpose, then prerequisites, then details. No redundant information. Every sentence contributes to clarity and is well-structured.

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 complexity (17 parameters, 3 required, nested objects, no output schema), the description covers prerequisites, association details, and scopes. It lacks explicit mention of return values or behavior on failure, which would improve completeness, but overall it is reasonably comprehensive.

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 adds value by explaining the purpose of additionalProperties and the override parameters for association type IDs, which are not fully detailed in the schema. This enhances understanding beyond the built-in descriptions.

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 'Create a HubSpot Quote and associate it to a deal and line items in a single operation.' It specifies the verb (Create) and resource (HubSpot Quote), and distinguishes itself as a high-level helper wrapping the standard endpoint, differentiating from siblings like hubspot_crm_create or hubspot_associations_create.

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 lists prerequisites: deal and line items must already exist, and suggests using hubspot_crm_create to create line items first. Provides guidance on overriding association type IDs and verifying IDs with hubspot_associations_labels_list. Mentions required scopes, giving clear context for when to use this tool versus alternatives.

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