Update post

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

With no annotations provided, the description carries the behavioral burden. It adds useful behavioral context, notably that setting scheduledAt to null clears the schedule and moves the post to draft. However, it does not disclose permissions, reversibility, status transition rules, or side effects on existing media or threads.

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 a single dense sentence with no filler. It front-loads the core behavior ('Partially update a post') and packs the key fields plus the important scheduledAt-null behavior into a compact format.

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 12 parameters, no annotations, and no output schema, this description is not complete enough. It covers only a subset of parameters and lacks usage guidance and behavioral details needed to safely invoke an update operation with this complexity.

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 very low (8%), so the description must compensate. It adds meaning for caption, media, schedule, status, poll, and thread, but omits several non-obvious parameters like accountIds, delayMinutes, firstComment, and accountOverrides, leaving them undocumented.

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 a specific verb and resource ('Partially update a post') and lists the updatable fields. However, it does not explicitly distinguish itself from the sibling reschedule_post, which also handles scheduling, so it is clear but not fully differentiated.

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?

No guidance is given about when to use this tool versus alternatives like schedule_post, reschedule_post, or create_post. The description implies usage through 'partially update' but does not provide exclusions or conditions.

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