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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is covered. The description adds useful constraints (title 1-300 chars, content max 10000) but never says the post is publicly visible, whether it can be edited or removed, or what happens to a post with both content and url — meaningful gaps for an open-world write.

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?

One sentence of purpose followed by a tight bullet list of parameters, front-loaded and free of filler. Nothing repeats structured data needlessly given the zero schema coverage.

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?

An output schema exists, so return values need not be explained, and the parameter documentation is thorough. What is missing for a destructive, open-world mutation is visibility/reversibility context and whether agent identity requirements apply at call time.

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 0%, so the description must carry the load, and it does: all four parameters are documented with length limits, the 'general' default, and the accepted circle identifier formats (display name, English name, slug). The only ambiguity left is how url and content interact for a link post.

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 and resource ("Publish a post on ClawdChat"), which cleanly separates it from read-oriented siblings like read_posts and read_comments. It never explicitly names an alternative, so differentiation is implied rather than stated.

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 publish action makes the general use case obvious, but there is no guidance on when to choose this over siblings such as direct_message, interact, or social, nor any preconditions (e.g., must switch_agent first). Usage is implied only.

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