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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds no behavioral context beyond the endpoint, such as permission requirements, workspace-scoped side effects, approval flow behavior, or retry semantics.

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 short, but this is under-specification rather than effective conciseness. It provides only the endpoint string and no explanatory content, so it does not earn its place as a useful tool 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?

Given a nested body schema, approval options, workspace permissions, and many sibling post-related tools, a one-line endpoint is not complete enough. The schema and annotations carry the load, but the description fails to explain what creating a post entails or how this tool relates to the other post and content tools.

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 67%, and the description itself adds no parameter meaning. The required body object lacks a description, and while property names like content, scheduledAt, and approvalMode are reasonably self-explanatory, the description does nothing to clarify payload semantics or parameter relationships.

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 states only 'POST /v1/posts', which conveys a create-post endpoint through REST convention but never says in plain language that it creates new posts. It is not a tautology, but it relies on the agent inferring meaning from the HTTP method and path rather than an explicit purpose statement.

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 about when to use this tool versus siblings such as patch_posts_id, delete_posts_id, or post_posts_postId_comments. The description gives no selection criteria, prerequisites, or alternative routing information.

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