ghl_saas_enable_location_deprecated

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

The description adds token requirement and plan restriction beyond annotations, which are minimal. However, it does not detail side effects or what enabling SaaS entails beyond the schema, leaving some behavioral ambiguity.

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 verbose and repetitive, containing HTML-like formatting and duplicate deprecation notices. It could be streamlined to front-load key information.

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?

Provides necessary context for a deprecated tool, including replacement endpoint and authorization requirements. Lacks information on whether the tool still functions or if calls will fail.

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%, so the description adds no extra value for parameters. The schema already documents parameter purposes and constraints effectively.

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 enables SaaS for a sub-account (location) and is deprecated, superseded by another endpoint. The purpose is specific and distinguishable from sibling tools like ghl_saas_enable_location.

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?

Explicitly states it requires an agency-level token, is only available on the Agency Pro plan, and is deprecated in favor of a replacement. Provides clear context for when it might be used and when to avoid it.

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