ghl_conversation_user_subscription_change

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

The description discloses a key side effect: 'Legal forms are automatically created for user-initiated resubscribe actions on custom subscriptions.' However, it does not address idempotency, rate limits, or outcomes if the subscription is already in the desired state. Annotations provide no additional behavioral hints, so the description carries the full burden and only partially fulfills it.

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 three sentences: title, purpose/behavior, and endpoint. It front-loads the core purpose and is reasonably concise. The endpoint line could be omitted as it's technical detail, but the overall structure is efficient.

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 nested input schema and no output schema, the description covers the main action and side effects but omits prerequisites, required parameters, and expected return. The endpoint info provides context but does not substitute for missing output behavior.

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 input schema has 100% coverage with descriptions for all parameters, including detailed enums and examples for subscription_action. The description adds high-level context ('Supports individual custom subscription changes and resub all functionality') but does not augment specific parameter meanings 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 'Process subscription change initiated by a user (admin/agent)' and enumerates supported actions (individual custom subscription changes, resub all). This provides a specific verb and resource, distinguishing it from sibling tools like ghl_conversation_get_contact_unsubscription_status.

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 implies when to use (user-initiated subscription changes) but does not explicitly state when not to use or mention alternatives. The mention of 'legal forms are automatically created' gives context, but no direct guidance on tool selection versus siblings like status-check or subtype creation tools.

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