List Subscriptions

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safe read-only nature is covered. The description adds useful behavioral context by specifying 'active' subscriptions and location scoping, but it does not disclose pagination behavior, default limit, or what happens when locationId is omitted.

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 a single, concise sentence that is front-loaded with the verb and resource. It contains no fluff or redundant information, and every word contributes to understanding the tool's purpose.

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 simple list tool with rich annotations, the description provides the core purpose but leaves out important operational details such as pagination via limit, whether locationId is required, and what the response contains. Given the low schema coverage and no output schema, the description is adequate but not fully complete.

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 0%, so the description must compensate. It mentions 'for a location' which loosely maps to locationId, but it does not explain the limit parameter, nor does it clarify whether locationId is required. The schema provides numeric constraints for limit but no semantic meaning, leaving gap.

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 ('Get'), the resource ('subscriptions'), and the scope/qualifier ('active', 'for a location'). It distinguishes this tool from siblings like ghl_list_pipelines and ghl_list_campaigns by specifying subscriptions and the active-status filter.

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 usage when you need active subscriptions for a location, but it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or alternative tool references. A clear context is present, but no direct guidance is given.

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