skool_posts_get

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

With no annotations, the description carries the full behavioral disclosure burden. It does usefully state that the response includes full content and comments, but it omits other behavioral context such as what happens when the slug is invalid, whether community defaults matter, or any rate/error behavior. The 'get' verb implies read-only safety, but no explicit safety statement is made.

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 two short sentences: first states the action and outcome clearly, second provides the required input. There is no filler or repetition; every sentence contributes essential information.

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 two-parameter get operation with no output schema, the description is largely complete: it states what is returned (full content and comments), where to obtain the required slug, and the schema covers the optional community parameter. It could be slightly richer by mentioning default community behavior or error/not-found handling, but these are minor gaps for this tool's complexity.

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%, so the schema already documents both postSlug and community. The description only repeats the slug source ('name field from posts list') already present in the schema, adding no new semantic information about the community parameter or value formats.

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 the tool retrieves a single post with full content and comments, using the specific verb 'get' and resource 'single post'. It naturally distinguishes itself from sibling tools like skool_posts_list by emphasizing 'single', and it specifies the required identifier ('post slug').

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 usage: you use it when you need a single post's full content and comments, and you need to have the post slug from a posts list. However, it does not explicitly name alternatives or state when not to use it, such as 'use skool_posts_list to browse posts first'.

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