publish_story

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

There are no annotations, so the description carries the burden of explaining side effects, authentication needs, or reversibility. It only adds the input constraints 'exactly one' and 'PUBLIC https', which are more about parameters than about what happens when the story is published.

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 very short and front-loaded, with no filler. The 'PUBLIC https' phrase is somewhat elliptical, but the overall definition is compact and scannable.

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?

With only three parameters and an output schema, a brief description can be sufficient. Still, the missing account semantics and lack of any note about authenticated default accounts leave a notable gap for an agent that must decide whether to pass account or rely on prior setup.

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?

The schema has zero property descriptions, so the description partially compensates by explaining that image_url and video_url are mutually exclusive and must be public HTTPS URLs. However, the meaning and behavior of the 'account' parameter are completely unexplained, and the schema allows an empty object despite the claimed 'exactly one' rule.

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 states the operation: publish a Story, an image or video. It distinguishes this from sibling tools like publish_image, publish_video, publish_reel, and publish_carousel by naming the Story resource explicitly.

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 clear context that this is for Story publishing and that exactly one media URL is needed. However, it does not explicitly say when to prefer this over publish_image, publish_video, publish_reel, or publish_carousel, nor does it mention prerequisites such as account setup.

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