Update Post

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

Beyond the annotations, the description discloses critical behavioral traits: partial update semantics, the platforms parameter replacing the entire target set, mediaUrls only applying together with platforms, and status-verification behavior on scheduled posts. It also notes the error message for invalid states and states the return value.

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 dense but every sentence earns its place, given the tool has 24 parameters and several non-obvious behaviors. The most important constraints—status restriction, partial updates, and platforms replacement—are front-loaded before lower-level details, making the critical information easy to absorb.

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?

With a rich schema, output schema, annotations, and sibling list, the description covers everything an agent needs: valid input states, partial vs. replacement semantics, cross-tool dependencies, return value, and explicit routing to sibling tools. Nothing material is left to inference.

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?

Although schema coverage is 100%, the description adds meaning beyond the schema by explaining idempotent omission behaviors for text, contentType, scheduledAt, timezone, and thumbnail, and by calling out the non-obvious destructive effect of sending platforms. It also clarifies the mediaUrls dependency and the TikTok/Pinterest required config fields.

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 a precise verb and resource: 'Update a DRAFT or SCHEDULED post in place.' It clearly distinguishes itself from sibling tools by naming publish_draft, delete_post, and create_post, so an agent can immediately tell what this tool is for and what it is not for.

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 gives explicit when-to-use guidance and exclusions: published posts cannot be edited, publish_draft should be used to change a draft's status, delete_post to cancel, and create_post for new posts. It also tells the agent where to source mediaUrls values (upload_media), covering both usage and alternatives.

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