ghl_saas_get_location_subscription_deprecated

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds important context: the need for an agency-level token and the endpoint details. No contradiction with annotations.

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 somewhat verbose with repeated deprecation notices and redundant endpoint info. Key information (deprecation, token requirement) is front-loaded, but could be more concise.

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 deprecated tool with no output schema, the description provides necessary context (deprecation, alternative, endpoint, token requirement) but does not describe return values. Adequate for decision-making 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?

Parameter coverage is 100% as both parameters have descriptions in the schema. The description does not add further detail about the parameters beyond the schema.

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 is deprecated, superseded by another endpoint, and fetches subscription details for a specific location. It identifies the verb (Get) and resource (Location Subscription Details) but does not explicitly distinguish from the non-deprecated sibling ghl_saas_get_location_subscription.

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 indicates deprecation and suggests an alternative, and specifies that an agency-level token is required. However, it lacks explicit guidance on when to use this tool versus the non-deprecated version, leaving the agent to infer.

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