Create post

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior: the result is a draft and nothing is scheduled or published, plus a validation dependency on describe_platform. It stops short of describing the return value or partial-failure behavior across multiple accountIds.

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?

Two short clauses, zero filler, and the most decision-relevant fact (draft, no scheduling) is front-loaded before the prerequisite. Every sentence earns its place.

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 seven-parameter creation tool with no output schema, the definition covers the key semantic (draft, nothing published) and the required setup call. It omits what is returned (e.g. post ids) and how multi-account creation behaves on partial failure, which would matter for a batch-capable write.

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 all seven parameters are already documented in the schema. The description only references scheduledAt, which is not even a parameter, and adds no format or syntax guidance for caption, postType, threadParts or accountOverrides. Baseline 3 applies when the schema carries the load.

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?

States a specific verb and resource ("Create a post") plus the crucial scope qualifier that it is "saved as a draft — no scheduledAt," which is exactly what separates it from the sibling schedule_post. An agent can pick this over schedule_post without opening either schema.

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?

Gives an explicit prerequisite ("Call describe_platform first for per-platform required fields") and implies the draft-vs-scheduled split. It does not explicitly name schedule_post as the alternative when a publish time is desired, so routing is clear but not fully spelled out.

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