social_media_posting_get_post

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds no extra behavioral context—no mention of return format, side effects, or dependencies. It does not contradict annotations, but it fails to contribute beyond 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?

The description is extremely short but under-specified. It lacks structure and front-loads no useful information. This is not conciseness that earns its place; it is insufficient to guide an agent effectively.

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's simplicity, the description is incomplete. It does not explain what constitutes a 'post', what information is returned, or how the ID and locationId parameters relate. Essential context for correct invocation 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?

Schema description coverage is 100%, with 'Post Id' and 'Location Id Defaults to GHL_LOCATION_ID when omitted' provided in the schema. The description itself does not elaborate on parameter semantics, but per the rule, a high-coverage schema sets a baseline of 3.

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 'Get post' states a clear verb and resource, indicating the tool retrieves a post. However, it does not specify that it retrieves a single post by ID, nor does it distinguish from sibling tools like social_media_posting_get_posts (plural). It provides minimal context, though it is not a pure tautology.

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?

There is no guidance on when to use this tool versus alternatives such as get_posts, create_post, or edit_post. The description does not mention any prerequisites, exclusions, or scenarios that would favor this tool.

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