ghl_blog_post_list

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. The description adds valuable behavioral context: paginated (limit, offset), requires blogId and limit, and the exact endpoint and OAuth scope. No side effects are mentioned (as expected for read-only), but the pagination details enhance transparency.

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 contains some redundancy, e.g., 'Get Blog posts by Blog ID' repeated, and information about the API title could be streamlined. It is not excessively long but could be more concise. The structure includes a clear first sentence defining purpose, but the rest is somewhat messy.

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 tool has 6 parameters and no output schema, the description covers main purpose, required params, pagination, and authentication. However, it omits explanation of locationId or the status/searchTerm filters, and does not hint at the response structure. It is adequate 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?

The description explains blogId, limit, and offset as required for pagination, but fails to explain locationId (required) or the optional status and searchTerm parameters beyond the schema's minimal documentation. Schema coverage is low (17%), and the description does not fully compensate.

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 'Lists all posts for a given blogId' and explicitly distinguishes it from a single-post fetch. The verb 'lists' and resource 'posts for a given blogId' are specific. Among siblings like ghl_blog_post_create and ghl_blog_update_post, this tool's purpose is distinct as a list operation.

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 required parameters (blogId + limit), pagination, and OAuth scope. It implies this tool is for listing all posts, not a single post, but does not explicitly list alternative tools or when not to use. The context is clear but lacks explicit exclusions.

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