List social accounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scoping ('Social Planner') and purpose ('use returned account ids when creating a post'), but does not disclose additional behavioral details such as pagination or response structure. This is adequate but not rich.

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?

Two concise sentences with no fluff. The primary action is stated first, and the second sentence provides the key downstream usage. Every word earns its place.

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?

For a simple list operation with one optional parameter, read-only annotations, and no output schema, the description is nearly complete. It explains the scope and the intended use of the result. A brief note on what fields are returned beyond ids would make it fully complete.

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% and the sole locationId parameter is already self-explanatory ('GHL Location (sub-account) ID. Defaults to GHL_LOCATION_ID.'). The description does not add meaningful parameter details beyond the schema, which is acceptable given the baseline for full schema coverage.

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 the action ('List') and the resource ('social media accounts connected to the location's Social Planner'). It also explains the output's downstream purpose (account ids for creating a post), which distinguishes it from sibling tools like ghl_list_media or ghl_list_social_posts.

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 provides clear context: it is for accounts connected to the Social Planner and the returned ids are meant to be used when creating a post. This implies when to use the tool, though it does not explicitly name alternatives or state when not to use it.

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