Get subscription

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

The annotations declare readOnlyHint=true and openWorldHint=true. The description's 'Fetch' is consistent but adds no extra behavioral context beyond what annotations already provide. It does not disclose error behavior, auth requirements, or response format, so it offers minimal additional transparency.

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 one-sentence description is concise and front-loaded. However, it is so brief that it under-specifies required context, skipping parameter semantics and usage. It earns a high mark for brevity but not for completeness.

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?

Given the lack of an output schema, low parameter coverage, and no usage guidance, the description is inadequate for a tool that requires correct subscription identification. An agent would lack clarity on what to supply and what to expect in return, other than the basic fetch action.

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 only 50% (locationId is described, subscriptionId is not). The description does not elaborate on any parameter, failing to compensate for the gap. With no parameter detail, an agent may not know that subscriptionId is the primary identifier and locationId is optional with a default.

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 it fetches a single subscription by id, with a specific verb and resource. It doesn't explicitly distinguish from the sibling ghl_list_subscriptions, but 'by id' implies it targets one record, so the purpose is clear.

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?

No guidance is provided on when to use this tool versus alternatives such as ghl_list_subscriptions. There is no context about required prerequisites (e.g., location context) or exclusions, leaving the agent to infer usage.

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