ghl_saas_bulk_disable

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

Adds security context (agency token) beyond annotations, but does not describe side effects or what 'disable' entails (e.g., reversible, billing impact). Annotations do not contradict the description.

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?

Description is concise with important warning front-loaded. Some redundancy ('Disable SaaS for locations' appears twice) reduces polish slightly.

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 essential information (endpoint, token requirement) but lacks details on return value, error conditions, and post-disable effects. Partially complete given no output schema.

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 description coverage is 50%, but the description adds no new parameter details. 'companyId' is mentioned in the endpoint but its purpose is not explained. The description relies on the schema for parameter meaning.

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 action (disable), resource (SaaS for locations), and input (locationIds). It also includes the endpoint, distinguishing it from sibling tools like ghl_saas_bulk_enable and 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 requires an agency-level token, telling the agent when this tool is appropriate. It implies not to use without such a token or for single-location operations, though it does not list alternative tools explicitly.

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