update_post

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

No annotations provided, and the description does not disclose behavioral details such as whether changes are reversible, what happens to existing media or schedule, or any validation rules. It only implies mutation, leaving significant gaps.

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?

Extremely concise with two sentences, no unnecessary words. The purpose is front-loaded and the instruction is clear.

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 no output schema, no annotations, and seven undocumented parameters, the description is severely incomplete. It lacks return value info, error cases, prerequisites, and parameter details, making it insufficient for correct tool invocation.

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 0%, and the description adds no meaning to the seven parameters. The generic hint 'pass only the fields you want to change' does not explain any parameter's purpose or constraints.

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?

Clearly states it updates a draft or scheduled post, with a specific verb (update) and resource (post). Distinguishes it from siblings like create_post, delete_post, get_post, and publish_post.

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?

Provides the instruction to pass only fields to change, which implies partial updates. However, it does not specify when to use this tool versus alternatives (e.g., creating a new post) or explicitly state that only draft or scheduled posts can be updated.

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