hubspot_get_deal_associations

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

Stated 'READ-ONLY' which is helpful, but no other behavioral traits disclosed (e.g., required permissions, rate limits). Since no annotations, description carries full burden and provides minimum viability.

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?

Single, front-loaded sentence with no wasted words. Every element earns its place.

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 simplicity of the tool (one parameter, output schema present), the description is nearly complete. However, lack of usage guidelines and parameter explanations slightly reduces completeness.

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?

Only one parameter (deal_id) with no description coverage. The description does not add meaning beyond the parameter name, which is self-explanatory but lacking context like format or required properties.

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 'Get contacts and company associated with a HubSpot deal' with a specific verb and resource. Distinguishes from sibling tools like hubspot_get_contact_associations.

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?

No guidance on when to use this tool versus alternatives like hubspot_get_contact_associations or when not to use it. Implicitly for deal associations, but no explicit context.

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