post_action

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

Annotations only provide openWorldHint and idempotentHint; notably there is no destructiveHint, so the mutation surface is not covered structurally. The description adds a useful scoping detail for hide_reply/unhide_reply ('replies to your own posts'), but says nothing about reversibility, permission requirements, or failure behavior beyond what the action pairs imply.

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?

A single front-loaded sentence that states the interaction target first and then the available verbs. No filler, no repetition, appropriately sized for the tool.

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 and thin annotations (no destructiveHint), the description leaves gaps: post_id provenance and format, account resolution, and what a call returns or how errors surface. It is adequate to select the tool but incomplete for confident invocation.

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 only 33% (account is the sole documented parameter), and the description merely re-lists the action enum values already present in the schema, which earns no credit. Only the parenthetical about own-post replies adds semantics; post_id's expected format (ID vs URL) is left entirely undefined in both places.

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 names a specific resource (a post) and fully enumerates the eight supported verbs, so an agent knows exactly what the tool mutates. It is clearly separable from create_post/delete_post and from the sibling user_action, though it does not explicitly call out that distinction.

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?

There is no when-to-use guidance: no mention of how to obtain post_id (e.g., via get_posts or search), no note that account must come from list_accounts (that hint lives only in the schema), and no exclusion conditions. Usage must be inferred entirely from the action names.

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