ghl_saas_update_saas_subscription

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

Annotations indicate idempotentHint=true and destructiveHint=false, which are consistent with the update operation. The description adds context about the required agency token and the operation's purpose, complementing the annotations without contradiction.

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 somewhat verbose with redundant phrases ('Update SaaS subscription' appears twice) and includes non-essential endpoint information. While front-loaded with key points, it could be more concise without losing clarity.

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 description covers purpose and auth requirements but lacks details on parameter semantics and return values. Given the nested body and multiple required fields, more guidance on using the tool correctly would improve completeness. No output schema is provided, which is acceptable but the description could compensate.

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 schema has 50% description coverage, with property descriptions being minimal (e.g., 'Company ID'). The tool description does not elaborate on how parameters like subscriptionId or body affect the subscription plan/pricing change, missing an opportunity to add meaning beyond the schema.

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 tool updates an existing SaaS subscription's plan/pricing for a location, using specific verbs and resources. It also corrects a misleading previous name. However, it does not explicitly differentiate from similar sibling tools like ghl_saas_update_rebilling.

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 explicitly requires an agency-level token and notes the security restriction (Agency-Access-Only), providing clear guidance on when the tool can be used. It does not mention alternatives or when not to use it, but the token requirement is a strong usage signal.

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