ghl_social_set_accounts

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation behavior is expected. The description adds endpoint and OAuth scopes but no additional behavioral traits like side effects, authorization requirements beyond scopes, or idempotency. With annotations covering the basics, a score of 3 is appropriate.

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?

Description is short and to the point, but the first line 'Set Accounts' is redundant with the tool name. The remaining content is efficient. One unnecessary line prevents a 5.

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 description mentions CSV import context, which is helpful. However, there is no output schema, and no explanation of how this tool fits in a larger workflow (e.g., after CSV upload, before posting). Siblings include related CSV import tools, but the description does not connect them.

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 description coverage is 100%, so all parameters are documented in the input schema. The description does not add any parameter meaning beyond what is in the schema. Baseline 3 is correct.

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?

Description clearly states 'Set social media accounts for a CSV import to publish posts to', which is a specific verb+resource combination. This distinguishes it from other social tools like ghl_social_post_create or ghl_social_get_account.

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 on when to use this tool versus alternatives. It implies a CSV import workflow but does not explain prerequisites, order of operations, or when to call this tool instead of other social account management tools.

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