skool_posts_create

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context by stating 'Requires auth cookies' and 'Posts to api2.skool.com', but it does not disclose return values, error handling, permission scopes, or what happens on failure. The mutation side effect is clear from the word 'create', but additional behavioral details are sparse.

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 that immediately convey the primary purpose and key operational requirements. There is no redundant or filler content, and the structure is front-loaded with the main action.

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 create operation with complete parameter schema, the description is minimally adequate. However, because there is no output schema, the agent is left uninformed about the return value or error responses. The auth cookie mechanism is also not explained (e.g., how to provide cookies), which could hinder invocation in some environments. These gaps make it only partially complete.

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 schema provides descriptions for all four parameters (label, title, content, groupId), achieving 100% coverage. The description adds no additional parameter semantics beyond what the schema already states, so the baseline score of 3 is appropriate.

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's function: 'Create a new post in a community.' The verb 'create' and resource 'post' are specific, and it distinguishes from sibling tools like skool_posts_list (read), skool_posts_get (read), and skool_posts_comment (comment).

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions that it requires auth cookies and posts to a specific endpoint, but does not explain when to prefer this over skool_request or other post-related tools, nor are any exclusions or alternative scenarios described.

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