ghl_social_clone_queue_item

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

The description adds the requirement for an active edit session beyond the annotations (readOnlyHint=false, destructiveHint=false), which is valuable. However, it does not detail side effects or output behavior, nor does it contradict annotations.

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 brief and front-loaded with the action, but includes endpoint and OAuth scope details that are likely redundant for an AI agent. Still, it is efficient and under two sentences.

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 covers the key prerequisite (active edit session) but lacks information about the return value or output, which is not compensated by an output schema. Given the tool complexity and no output schema, more detail would be beneficial.

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 descriptions for nested properties like order, sessionId, and locationId, but the top-level description for body is generic. The tool description does not add additional semantic meaning beyond what the schema already provides, resulting in minimal added value.

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 verb 'Clone' and the resource 'queue item', and specifying 'Duplicates an existing queue item at a specified order position' distinguishes it from sibling tools like create, update, or delete queue items.

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 notes the prerequisite of an active edit session, providing important usage context, but does not explicitly compare to alternatives or state when not to use this tool versus other duplication methods.

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