ghl_saas_get_locations_by_stripe_id

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

Annotations already indicate read-only and idempotent behavior. The description adds security requirement (agency token) and endpoint version, but does not describe output format or side effects. It adds some value beyond annotations but is not comprehensive.

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 repetitive (two similar sentences about getting locations) and could be more concise. However, it is front-loaded with the security warning and includes endpoint info, so it is reasonably structured.

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?

No output schema, so description should cover response. It does not mention what the response contains or if pagination exists. Given 3 required params and no output schema, the description is incomplete for full understanding.

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 coverage is 0%, so description should compensate. It explains that customerId and subscriptionId are stripe identifiers and required, but does not explain companyId or provide format or examples. Adds some meaning but insufficient for missing schema documentation.

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 retrieves locations by stripe customer or subscription ID, with companyId requirement. It distinguishes from the deprecated version by noting parameter requirement differences, making the purpose unambiguous.

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?

Provides explicit guidance: requires agency-level token, both customerId and subscriptionId are required, and differentiates from the deprecated twin. This helps the agent decide when and how to use the tool correctly.

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