ghl_social_create_queue_item

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds that the tool creates a new item and offers two modes (session or direct), but does not disclose further behavioral traits beyond what annotations and the input schema already provide.

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 concise: 4 sentences, first sentence is the core action, then adds usage modes and endpoint/scopes. No wasted words, information is front-loaded.

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?

Given the complexity of nested objects and no output schema, the description is sparse. It does not explain the difference between session and direct modes, prerequisites, or return format. However, the input schema has extensive inner descriptions, so the description is minimally 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?

The input schema covers 50% of parameters with descriptions (e.g., body has many nested property descriptions, but queueId has no description). The tool description does not add meaning for queueId or emphasize key parameters beyond the schema. Baseline is 3 due to moderate 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 'Create a new item in the queue' and 'Adds a new post item to a queue,' specifying the exact verb and resource. It distinguishes from siblings like ghl_social_create_queue (which creates a queue) and ghl_social_update_queue_item (which updates).

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 mentions using sessionId for edit sessions or directToQueue for immediate addition, but does not provide explicit guidance on when to choose this tool over alternatives like ghl_social_clone_queue_item or ghl_social_update_queue_item. Usage context is implied but not contrasted.

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