ghl_saas_get_locations

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is clear. The description adds the agency token requirement, which is valuable, but does not elaborate on other behavioral aspects like rate limits or error conditions.

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 paragraph with inconsistent capitalization (REQUIRES, `page`), redundant 'Get SaaS Locations', and an endpoint line that is more technical than helpful. It is not well-organized and 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?

With 2 required params, no output schema, and annotations covering safety, the description is incomplete. It does not explain the return format, pagination details (e.g., page size, max pages), or how to iterate through results. The endpoint info is extra but not essential for an agent.

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%. The description mentions `page` as a required query param and vaguely mentions pagination, but does not explain `companyId` or provide details like default values, formats, or how to handle pagination. The phrase 'pass them to page through full result sets' is unclear.

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?

Description clearly states it fetches SaaS-activated locations for a company with pagination. However, it does not distinguish itself from sibling tools like the deprecated version or the stripe ID variant, leaving some ambiguity.

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 mentions the requirement for an agency-level token but provides no guidance on when to use this tool versus alternatives (e.g., deprecated versions, stripe ID version). No when-not-to or alternative references.

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