List Social Media Posts

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the scope of 'scheduled and published' posts, which provides context beyond the annotations. However, it does not disclose pagination behavior or any filtering nuances, so the transparency 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?

The description is a single concise sentence that directly states the tool's purpose with no unnecessary words. It is front-loaded and easy to parse. 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?

The tool is relatively simple with two optional parameters and no output schema, but the description does not explain parameter roles or return values. The annotations help with safety, but the agent lacks crucial invocation details such as whether locationId is required or how to handle large result sets. The description is minimally complete for a simple list operation but has clear 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?

The input schema has two parameters (limit and locationId) with zero description coverage. The description does not mention either parameter, leaving their meaning and usage entirely unexplained. An agent would have to guess that limit controls pagination and locationId filters by location, but there is no textual support. This is a significant gap.

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 tool retrieves social media posts, specifically those scheduled and published. It uses a clear verb ('Get') and a specific resource ('social media posts'), which distinguishes it from sibling tools like ghl_create_social_post and ghl_list_social_accounts. However, it does not explicitly contrast itself with other list tools, but the resource is unique enough.

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?

There is no guidance on when to use this tool versus alternatives, such as ghl_list_social_accounts or ghl_create_social_post. The description does not mention exclusions, prerequisites, or typical scenarios. The usage is only implied by the tool name and brief description.

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