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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is known. However, the description adds zero behavioral context on top of that—it does not explain partial-update semantics, what happens when scheduledAt is set to null versus omitted, or whether status changes trigger side effects. No contradiction with annotations, but no added value either.

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 short, but this is under-specification, not conciseness. A bare HTTP method and path string carries no decision-relevant information beyond what the tool name already encodes, so nothing in the description 'earns its place'.

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?

An output schema exists, so return values need not be explained, but this is a complex, destructive mutation tool with nested body semantics and an eight-state workflow enum. The description leaves the agent to infer everything from the schema, including the meaning of the id, state-transition rules, and how this endpoint relates to the several nearby patch/put/delete siblings.

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 only 33% (only workspaceId is described), and the description text contributes no parameter meaning at all. The body schema's enums (status workflow states, approvalMode) carry real semantic weight, but the description fails to explain their interplay—e.g., whether scheduledAt requires status='scheduled' or which status transitions are valid.

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 'PATCH /v1/posts/{id}' merely restates the tool name in HTTP endpoint form; it adds no semantic content about what the tool does. It does not state what fields are updated, what resource lifecycle it touches, or how it differs from siblings like patch_posts_id_content_channelId or put_posts_id_content_channelId_media.

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 use this tool versus alternatives. Closely related siblings exist (post_posts, put_posts_id_content_channelId_media, patch_posts_id_content_channelId), yet the description offers no conditions, exclusions, or routing hints to help an agent choose correctly.

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