ghl_social_set_google_locations

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds no behavioral traits beyond the endpoint. It does not disclose side effects (e.g., whether existing locations are overwritten) or authorization requirements.

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 very concise but poorly structured for an agent. The endpoint detail is secondary and not front-loaded. It lacks a clear separation of purpose from technical details, and every sentence is not equally valuable for tool selection.

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?

The tool has a complex nested body (account, location, companyId) with no output schema. The description fails to explain the effect of setting locations, the structure of the body fields, or the expected response. Relies entirely on schema, which is insufficient.

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 100%, with basic descriptions for parameters (e.g., 'Account Id', 'Company ID'). The description adds no extra meaning to the parameters, repeating only the endpoint. Baseline 3 is appropriate as the schema already documents the parameters.

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 'Set google business locations' with an endpoint hint, clearly indicating the resource (Google business locations) and action (set). However, 'set' is ambiguous (create/update/overwrite) and does not explicitly distinguish from the sibling 'ghl_social_get_google_locations' tool.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context for when 'set' is appropriate compared to other social media tools, nor does it mention prerequisites or exclusions.

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