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

Annotations already state destructiveHint=true and idempotentHint=true, and the description adds no behavioral context beyond the literal DELETE method. It does not say whether the deletion is permanent, cascades to related content/comments/media, or what response is returned.

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 very short and free of fluff, but it is a bare endpoint template, not a structured explanation. It is economical enough yet sacrifices semantic detail for brevity.

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 tool with no auth/read hints and many sibling deletion endpoints, the description does not explain side effects, return shape, or how it differs from delete_post_content and delete_posts_postId_comments_id. An agent selecting among siblings would need more context.

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?

With 50% schema description coverage, the description should compensate for the undocumented path.id, but it only restates the URL template and adds no meaning about what id represents or how to supply it. workspaceId semantics are already documented in the input schema, so the description contributes little to parameter understanding.

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 endpoint string 'DELETE /v1/posts/{id}' clearly conveys a DELETE operation on a post resource, and the path shape distinguishes it from comment/content/media deletion siblings. It is a specific verb+resource, though it relies on the reader to infer that it deletes the post itself rather than a subresource.

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 description provides no indication of when to prefer this tool over delete_post_content or delete_posts_postId_comments_id, nor does it mention prerequisites or alternatives. It is only an HTTP method/path with no usage context.

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