ghl_association_create

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

Description provides OAuth scopes (associations.write) and endpoint, adding value beyond annotations. Annotations already show readOnlyHint=false and destructiveHint=false, so description confirms write operation and adds scopes.

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?

Short and front-loaded with purpose. The note 'will add more in the future' is slightly extraneous but not harmful.

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?

Lacks details on response format, error handling, or prerequisites. For a create operation with nested params, an example or clarification of key/label fields would improve 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?

Schema coverage is 100% with descriptions and examples for all properties. Description does not add significant meaning beyond the schema; baseline 3 is appropriate.

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 it creates associations between contact-contact and contact-custom objects, with a specific verb and resource. However, it does not differentiate from sibling tools like ghl_association_create_relation.

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 (e.g., creating relations vs. associations). No when-not-to-use or prerequisites described.

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