ghl_saas_bulk_enable

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

Adds security context beyond annotations (agency token required). Annotations indicate non-read-only and non-destructive, which align with 'enable'. No further behavioral details like idempotency or side effects.

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?

Concise at three sentences, front-loading the critical security requirement. Could be slightly more structured but is efficiently scoped.

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?

For a bulk operation with nested body and no output schema, the description lacks details about actionPayload, version differences, return values, and error cases. Incomplete for the tool's complexity.

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 description does not explain any parameters; the schema covers body properties but companyId is undocumented. Schema description coverage is 50%, and the description fails to compensate, especially for the missing companyId description.

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 'Enable SaaS mode for multiple locations with support for both SaaS v1 and v2', using a specific verb and resource. It distinguishes from siblings like *bulk_disable* and *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 warns 'REQUIRES AN AGENCY-LEVEL (Company) TOKEN — spec security is Agency-Access-Only', guiding token choice. Lacks explicit when-not or alternatives, but sibling names imply single location enable/disable alternatives.

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