Associate HubSpot Records

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds that it returns a 'Confirmation of the association created', but does not elaborate on side effects, error handling, or confirmation details. With annotations covering safety, the description provides marginal additional transparency.

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 concise and well-structured, with clear 'Args' and 'Returns' sections. Every sentence serves a purpose, and there is no extraneous content.

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 no output schema, the description usefully notes the return type ('Confirmation'). It covers the supported pairs and parameter types. However, it omits details like error messages or behavior when IDs are invalid, but for a simple creation tool it is largely sufficient.

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 each parameter has a basic description. The description adds significant value by listing the supported pairs (e.g., contacts↔companies), which are not indicated in the schema enums. This clarifies which combinations are valid, going beyond what the schema provides.

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 action ('Create an association'), specifies the resource ('HubSpot CRM records'), and gives concrete examples ('link a contact to a company'). It distinguishes from siblings like hubspot_list_associations by focusing on creation rather than listing.

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 lists supported pairs (contacts↔companies, deals↔contacts, deals↔companies), which implicitly guides when to use the tool. However, it does not explicitly state when not to use it or mention prerequisites (e.g., records must exist).

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