post_story

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

No annotations are present, so the description carries the full transparency burden. It does add useful behavioral context by specifying '24-hour' ephemerality and the exclusive input rule, but it omits auth/permission requirements, expected return value, and behavior when the exactly-one constraint is violated.

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?

A single, front-loaded sentence with no filler. Every word contributes either the core action, the content type, the input sources, or the exclusivity constraint.

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 simple two-parameter tool, the description covers the essential invocation constraint, but without annotations or an output schema, it leaves out what happens after publishing and how the caller learns the result. It is minimally viable but not fully complete.

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%, so the description must compensate. It clearly maps the two parameters to image and video URLs and adds the critical constraint that exactly one must be provided, which the schema does not express.

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 ('Publish'), a distinct resource ('24-hour story'), and the two acceptable input sources (image or video URL). The term 'story' clearly separates it from sibling tools like post_image and post_reel, so an agent can identify what this tool does immediately.

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 provides no guidance on when to use this tool instead of post_image, post_reel, or schedule_reel. The parenthetical 'provide exactly one' is a parameter constraint, not tool-selection context or an explicit when/when-not rule.

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