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

The description only restates the DELETE endpoint and adds no behavioral context beyond the annotations. It does not disclose what deleting content means for the post, whether the operation is reversible, or what side effects occur; annotations already supply destructiveHint/idempotentHint.

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 extremely terse and front-loaded, with no filler, but it is only a raw endpoint string rather than a structured explanation. It is concise without being a complete natural-language description.

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 destructive operation with nested parameters, a one-line endpoint does not fully explain scope, prerequisites, or effects. The output schema exists, so return values need not be detailed, but the lack of any usage or consequence guidance leaves important gaps.

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?

The path template gives meaning to the nested id and channelId parameters, which the schema otherwise leaves undocumented. workspaceId is described in the schema, so the description partially compensates for the 50% schema coverage, but does not explain the params in prose.

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 is an explicit DELETE endpoint path, so the verb and target resource (content of a post on a specific channel) are clear. It is distinct from siblings like delete_posts_id because the path includes /content/{channelId}, though it does not explain the operation in natural language.

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 guidance on when to choose this tool over delete_posts_id, delete_media_id, or patch_posts_id_content_channelId. The intended use is only implied by the HTTP method and path; no exclusions or alternatives are mentioned.

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