ghl_social_category_list

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the agent knows it is safe and non-destructive. The description adds behavioral context: the endpoint (GET), OAuth scopes, and pagination mechanism. No contradictions with 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 concise with three sentences and endpoint details, no fluff. The main purpose is front-loaded in the first sentence, followed by endpoint and OAuth info, then pagination guidance.

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 no output schema, the description omits details about the return type (list of categories) but covers pagination and required locatioparameter. The tool is straightforward, so the description is mostly complete. Could briefly mention the response structure.

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 each parameter. The description adds meaning by grouping limit and skip as pagination params and mentioning 'optional search', but does not provide additional semantics beyond the schema for locationId or searchText. Baseline 3 is appropriate.

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 'Get categories by location id' and 'Retrieve all categories for a specific location with optional search and pagination', providing a specific verb and resource. It distinguishes from sibling tools like ghl_social_category_get (singular) and ghl_social_fetch_available_categories by focusing on location-based listing with pagination.

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 implies usage for retrieving categories filtered by location with optional search and pagination, but does not explicitly state when not to use or compare to alternatives like ghl_social_category_get or ghl_social_fetch_available_categories. The guidance on pagination params (limit, skip) is helpful but lacks exclusion criteria.

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