hubspot_get_contact_associations

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

Explicitly marks the tool as READ-ONLY, a key behavioral trait, but with no other behavioral details (e.g., rate limits, required permissions) despite no annotations to fall back on.

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?

A single, concise sentence that places the key verb and resource at the start, with no wasted words. Ideal for quick scanning.

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?

The tool is simple (one required parameter) and has an output schema (not shown but assumed), so the description adequately covers purpose and key entities, though some may wish for more context on output structure.

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?

The only parameter contact_id has no description in the schema (0% coverage), and the description adds no extra meaning beyond stating what entities are returned, failing to explain ID format or constraints.

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 it gets companies and deals associated with a HubSpot contact, distinguishing it from sibling tools like hubspot_get_contact or hubspot_get_company.

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?

Indicates read-only nature, which is a usage guideline, but does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria.

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