Get social post

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

The description is consistent with the readOnlyHint=true and openWorldHint=true annotations, and the word 'Fetch' conveys a read operation. It does not add deeper behavioral context such as error handling, missing-post behavior, or location requirements, but the annotations lower the burden for this simple read tool.

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 a single front-loaded sentence with no filler. Every word earns its place and it is appropriately concise for a tool that performs one simple fetch operation.

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 simple read tool, the schema covers required and optional parameters, and the annotations cover the read-only nature. However, the description does not route the agent away from ghl_list_social_posts, and there is no output schema describing the response shape. The invocation is minimally sufficient but relies on inference.

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 phrase 'by id' adds minimal meaning by clarifying that postId is the lookup key, which is already implied by the schema. Schema coverage is 50%: locationId is described, while postId is not, but the description does not meaningfully compensate for the postId gap. Still, the parameter names and required field are straightforward enough for a basic get-by-id call.

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 a clear action ('Fetch'), a specific resource ('a single social post'), and a selection mechanism ('by id'), which distinguishes it from list/create/delete social post siblings. It does not explicitly name alternatives, but the singular and 'by id' wording makes the purpose unambiguous.

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 the tool should be used when a specific postId is known, but it provides no explicit when-to-use or when-not-to-use guidance and does not compare against ghl_list_social_posts or ghl_create_social_post. The intended usage must be inferred from the tool name and required parameter.

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