ghl_blog_get_post_by_id

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

Adds context beyond the annotations: it returns the post body, only published posts are eligible (so drafts will not resolve), and the call requires a location token with a specific OAuth scope. Annotations already declare readOnly/idempotent/non-destructive, and the description does not contradict them.

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?

Front-loaded purpose sentence followed by the return shape, endpoint, auth requirement and scope in a compact block. Minor redundancy in restating the tool name as the API name, but no wasted sentences.

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?

For a two-parameter read with no output schema, the description covers what is returned (the full post including body), the auth/scope requirement and the endpoint. Only a note on failure modes (e.g., unpublished or missing post) is missing.

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?

Both parameters are fully documented in the schema (100% coverage), so the baseline is 3. The description adds the path placement of postId and the location scoping of locationId but nothing about format or edge cases beyond the schema.

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?

States a specific verb and resource (get a single published blog post, including its content/body) scoped to a location. The word 'single' implicitly contrasts it with the sibling list tool ghl_blog_post_list, but no sibling is named explicitly, so it falls short of a 5.

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 supplies a prerequisite (a Sub-Account/location token and the blogs/posts.readonly scope) and the endpoint, which implies when the call is appropriate. It never states when not to use it or points to alternatives such as ghl_blog_post_list for discovery or ghl_blog_update_post for mutation.

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