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

Annotations cover the safety profile (write, open world, non-destructive), and the description adds meaningful behavior beyond them: the default per-post confirmation, the fact that it reaches other people, admin-only category constraints, and the required API key.

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 first two sentences restate the same idea twice ('Publish a post to the community feed in a category, as you' then 'Publishes a post to the feed in a given category, under your name'). Otherwise it's front-loaded and free of filler, but the duplication is wasted space.

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?

Covers auth needs, confirmation behavior, category permissions, and content format, which is sufficient for a create-post tool. With no output schema, only minor gaps remain (e.g., what the returned post/ID looks like).

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 coverage is 100% and already documents all four params including the 'Links and images by URL' note, which the description essentially repeats. The description adds little parameter meaning beyond the schema, so baseline 3 applies.

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 (publish) and resource (post to community feed in a category) and clarifies it posts under the caller's own name. This cleanly distinguishes it from siblings like skool_comment_on_post and skool_pin_post.

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?

Gives concrete conditions: admin-only categories require an admin account, confirmation is on by default and can be toggled off for this tool, and an API key with app access is required. It doesn't explicitly point to alternatives, but the usage context is clear.

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