ghl_location_update

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

The description complements annotations by stating OAuth scopes and token requirements. However, it does not clarify whether the update is partial or full replacement, nor does it mention response behavior or side effects beyond the mutation.

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 concise and front-loaded with the most critical information (token requirement, action, endpoint). Every sentence adds value, and there is no repetition or fluff.

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 the absence of an output schema, the description does not explain what the tool returns after a successful update, nor does it cover error handling or validation behavior. This makes it incomplete for an agent to fully understand the tool's effects.

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?

The input schema has 100% coverage with descriptions, so the tool description does not need to add parameter details. However, the schema's body description is generic ('carried verbatim from OpenAPI spec'), providing no additional insight for the agent.

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 that the tool updates a Sub-Account (formerly Location) by putting data to the endpoint. It distinguishes itself from sibling tools like create, get, delete, and search.

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 specifies that it requires an agency-level token, but does not explicitly state when to use this tool over alternatives like create or search. Usage context is implied but not formally guided.

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