ghl_oauth_get_installed_location

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds critical behavioral context: agency-level token requirement and pagination usage. 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?

Description has redundancy (repeats 'Get Location where app is installed' twice) and is not tightly structured. While not overly long, it could be more concise and better organized.

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 10 parameters, no output schema, and annotations present, the description covers auth, legacy status, and pagination but lacks explanation of return structure. It partially meets needs but has gaps.

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 has 100% parameter description coverage, so baseline is 3. Description adds minor value by flagging pagination parameters (skip, limit) and OAuth scopes, but does not elaborate beyond what schema provides.

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 states it gets a location where an app is installed, but the singular name conflicts with the plural endpoint and pagination parameters, suggesting it actually lists multiple locations. This ambiguity reduces clarity. Sibling tool 'ghl_oauth_get_installed_locations' further muddies distinction.

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?

Explicitly states required token type (agency-level) and notes it is a legacy twin with a preference for v3 alternative. This provides clear guidance on when and why to use the tool, but does not cover all alternatives.

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