update_post

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

No annotations provided, so description carries full burden. It discloses that updates apply to drafts and scheduled posts, but does not specify permissions, side effects (e.g., changing a scheduled post might affect its schedule), or that updating published posts is not allowed. Minimal behavioral context.

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?

Single sentence with a dash and period, no fluff. Clearly states the core action and scope. Front-loaded with key information.

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?

Covers main use cases and eligibility (drafts/scheduled), but missing details like required id, behavior on omitted parameters (remain unchanged vs reset), and whether updating scheduled posts triggers any side effects. For a complex tool with 8 params and nested objects, more completeness would help.

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 100% with each parameter having a clear description. The tool description only lists high-level categories (caption, media, etc.) without adding extra meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states 'Update an existing post by id' and lists the changable fields (caption, media, target accounts, schedule, platform_configurations). It distinguishes from siblings like create_post, delete_post, and schedule_post by focusing on modifying existing posts.

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 mentions 'Works on drafts and scheduled posts', implying the post must be in one of those statuses, but does not explicitly state when to use vs alternatives like schedule_post or publish_now. No exclusions or alternatives given.

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