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

It adds a useful, non-obvious behavior beyond the annotations: new posts are not search-indexed immediately. It is consistent with `readOnlyHint=false` and `destructiveHint=false`, but 'until they earn it' is vague and `indexable` is never defined.

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 brief, but it starts with the fragment 'The created post.' rather than a clear action statement. The indexing warning and endpoint are useful, but the structure is disjointed rather than front-loaded.

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 creation tool with four required parameters, the schema supplies most invocation detail. The main gaps are lack of alternative routing, a vague definition of how indexing is 'earned,' and no output schema to clarify the returned post object.

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 80% and the individual parameters are already documented with constraints like regex, min/max lengths, and examples. The tool description itself adds no parameter semantics, 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 tool name and title ('Publish a post') plus the explicit endpoint `POST /api/v1/community/posts` make the operation clear. However, the description itself does not directly say 'creates a community post' and offers no differentiation from siblings like `community_create_reply`.

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 given about when to call this tool versus alternatives. The search-indexing note is a behavioral consequence, not a usage criterion or an exclusion of another tool.

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