ghl_social_fetch_queues

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

The description indicates a read-only operation ('Retrieves') and includes OAuth scope 'socialplanner/category.readonly', but the annotations set readOnlyHint=false, creating a contradiction. The description does not disclose any side effects or additional behavioral traits beyond the annotations, which are themselves inconsistent.

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, covering the core purpose in the first sentence and adding technical details (endpoint, OAuth scopes) in subsequent lines. It is front-loaded and free of superfluous information, though the technical details could be seen as extraneous.

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?

No output schema is provided, so the description must convey return value information. It states 'paginated list of all category queues' but lacks detail on the structure or fields of a queue, leaving some ambiguity for an agent. Adequate for a basic list operation but incomplete.

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 coverage is 100% with descriptions for all parameters. The description adds context beyond the schema by stating that the result is a 'paginated list' and excludes deleted items, which enriches parameter understanding (e.g., skip/limit for pagination).

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 tool's purpose: 'Fetch category queues for a location' and elaborates with 'Retrieves a paginated list of all category queues for a given location, excluding any that have been marked as deleted.' It uses specific verbs and identifies the resource and scope, distinguishing it from siblings like ghl_social_fetch_queue_by_id.

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 does not explicitly state when to use this tool versus alternatives, nor does it provide when-not-to-use guidance or prerequisites. Usage is implied by the verb 'Retrieves', but without explicit comparisons or exclusions, it scores 3.

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