update_social_post

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

With no annotations, the description carries the full burden. It usefully discloses that live updates are limited to supported platforms (Facebook Page, YouTube) and that some platforms cannot edit published posts, but it omits mutation semantics such as overwriting existing content, failure behavior, or permission requirements.

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 two sentences, front-loaded with the core action and followed by the key conditional behavior. It is efficient, though the second sentence could be slightly tightened.

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?

For a mutation tool with 12 parameters and no annotations, the description covers the high-level purpose and platform limitation but leaves important behavioral context thin, such as overwrite semantics and what happens when unsupported platforms are targeted. The schema fills in parameter details, but behavioral completeness is only partial.

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%, so the schema already explains all 12 parameters, including updateOnPlatform and scheduling details. The description only briefly mentions updateOnPlatform, adding no meaningful parameter semantics beyond the schema.

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 specific verb ('Update or edit') and resource ('post content or schedule') in SocialDispatch, clearly distinguishing it from create/publish/delete siblings. It could be slightly sharper about how it differs from schedule_social_post for rescheduling, but the core purpose is unambiguous.

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?

It provides a clear conditional usage note for published posts via updateOnPlatform=true, but it does not explicitly say when to use this tool versus schedule_social_post or publish_social_post. The guidance is implied rather than stated as alternatives or exclusions.

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