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

Beyond the annotations (destructive, openWorld, non-idempotent), the description discloses confirmation-by-default, per-tool opt-out, queue timing, authorship attribution, and the review-status path. It does not say whether a created post can be edited or deleted afterward, which matters given destructiveHint=true.

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 opening sentence re-states the mode behavior that the next two sentences explain in detail, and 'Waits for the owner's approval.' is an orphan fragment whose subject is unclear. Content is front-loaded, but tightening would remove the duplication.

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 mutation tool with no output schema, it covers permissions, defaults, confirmation behavior, and the submitted status outcome. Return details are thin (no indication of what identifier comes back), but the calling information an agent needs is largely present.

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%, so baseline is 3, but the description adds real meaning: it explains the runtime consequence of each mode value and the review fallback, which the schema's terse 'post or queue' enum does not.

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 concrete verb and resource ('Creates a post under your name in a Space') and names the two modes, so it is clearly distinguishable from siblings like post_answer, ask_question, and review_space_submission. An agent can identify the operation without opening the schema.

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?

Explains role-dependent routing: post publishes immediately for admin/moderator/contributor, queue defers it, and follower-only Spaces go to admin review. It does not explicitly name a sibling alternative, but the role/mode guidance is clear enough to choose correctly.

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