ghl_social_media_accounts_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get social media accounts for a location,' offering no information about side effects, permissions, pagination, return format, or error behavior. This is a minimal disclosure that does not go beyond the tool's name.

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 what the tool does. It is appropriately sized for the simple scope of the tool, with no wasted words or redundant information.

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 no output schema and no annotations, so the description should explain what the return values look like or what 'social media accounts' entails. It does not, leaving the agent without critical information about the response structure. The description is insufficient for a complete understanding beyond the basic action.

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 schema covers the single parameter 'locationId' with a description and a default hint, so schema coverage is 100%. The tool description adds no additional semantic meaning beyond what the schema already provides, warranting the baseline score of 3.

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 ('Get') and resource ('social media accounts') scoped to a location, making the tool's purpose unambiguous. However, it does not explicitly distinguish this from sibling tools like ghl_facebook_connection_get or ghl_facebook_linked_pages_get, which also deal with social media-related resources, so it misses the top score for sibling differentiation.

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 no guidance on when to use this tool versus alternatives. It does not state any prerequisites, exclusions, or mention other tools that might be more appropriate for specific scenarios, leaving the agent without clear selection criteria.

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