ghl_social_fetch_queue_items

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

The description implies a read operation ('fetch'), but the annotation readOnlyHint=false contradicts that. No disclosure of side effects or other behavioral traits beyond basic description.

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 two sentences plus endpoint and OAuth scopes, which are not essential for an AI agent. It is reasonably concise but includes some technical details that could be omitted.

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 pagination and draft session, but lacks info on error handling, response format, or additional constraints. Adequate for basic use but not comprehensive.

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 already provides detailed descriptions and examples for all parameters within the body object. The tool description adds no extra parameter semantics.

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 it fetches items from a queue, returns paginated results, and mentions the sessionId for draft items. It differentiates from siblings like ghl_social_fetch_queues or ghl_social_fetch_queue_by_id, though not explicitly.

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 vs alternatives. The description only states what it does, not when to choose it over other queue-related tools.

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