ghl_blog_site_list

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

Annotations already declare readOnlyHint, destructiveHint, etc. The description adds value by specifying the endpoint, required OAuth scopes, and pagination parameters (skip, limit) for full result retrieval. This provides behavioral context beyond the 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 relatively short but includes extraneous technical details like the exact endpoint path with version header and source file path. This adds clutter without aiding an AI agent. It is front-loaded with the title, which is helpful, but could be more concise.

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 purpose, pagination, and OAuth scopes but omits the response structure, error handling, or the effect of the optional searchTerm parameter. Given the tool has 4 parameters and no output schema, the description provides adequate but not comprehensive context.

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 description coverage is only 25% (only searchTerm described). The description adds minimal parameter insight: it mentions 'Pagination params: skip, limit — pass them to page through full result sets' and implicitly references locationId in the title. The description does not explain locationId or searchTerm beyond what the schema already provides.

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 states 'Get Blogs by Location ID' and the tool name includes 'site_list', but it doesn't explicitly differentiate from the sibling tool 'ghl_blog_post_list'. The endpoint '/blogs/site/all' suggests it lists blog sites, but the description uses 'blogs' ambiguously. An agent might confuse it with listing blog posts.

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 is provided on when to use this tool versus alternatives like 'ghl_blog_post_list'. The description focuses on API details rather than use case differentiation. An agent receives no help in choosing between listing blog sites vs. blog posts.

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