ghl_oauth_get_location_access_token

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

Discloses that it generates a locationAccessToken from AgencyAccessToken, requires agency-level token, and uses form-urlencoded body. Annotations do not cover these details, so the description adds significant behavioral context beyond 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?

Front-loads critical info (requires agency token, form-urlencoded) in bold. Slightly verbose with version/source details, but every sentence adds value. No unnecessary repetition.

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?

Covers required parameters, authentication, and body format, but does not describe the response structure (expected token fields). For a simple token exchange, this is a notable omission. Without output schema, the description should clarify what is returned.

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 already covers both parameters (companyId, locationId) with descriptions (100% coverage). The description adds that they are form fields and not JSON, which is valuable beyond the schema. Baseline 3 plus extra context justifies 4.

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?

Clearly states it gets a location access token from an agency token, specifies the endpoint, and distinguishes itself as the legacy twin of a v3 operation. The verb 'Get' and resource 'Location Access Token' are precise.

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 requires an agency-level token, specifies the request body format (application/x-www-form-urlencoded), and advises to prefer the v3 operation for new integrations. Provides clear when-to-use and when-not-to-use guidance.

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