Create post

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose two key behaviors: the post is saved as a draft and is not scheduled. However, it does not mention side effects, permissions, validation failures, or whether anything is immediately published to connected accounts.

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 sentences with no wasted text. The most important behavioral distinction (draft, no scheduledAt) is front-loaded, and the prerequisite instruction is placed second. 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 tool with 7 parameters and no output schema, the description is thin. It correctly flags the draft behavior and the describe_platform prerequisite, but it does not describe the return value, what happens after creation, or how the many optional fields fit together. Still, the schema fills some gaps, so it is minimally viable.

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 documents each parameter. The description adds contextual value by pointing to describe_platform for per-platform required fields, but it does not explain how parameters like threadParts or accountOverrides interact 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 clearly identifies the operation as creating a post and immediately disambiguates it from scheduled publishing by noting it saves as a draft with no scheduledAt. This distinguishes it from sibling tools like schedule_post without needing to inspect schemas.

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 gives explicit pre-use guidance: 'Call describe_platform first for per-platform required fields.' It also implies when not to use this tool by stating draft-only behavior and no scheduledAt, though it does not explicitly name schedule_post as the alternative.

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