publish_story

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It mentions 'PUBLIC https' but does not explain side effects, authentication needs, rate limits, or what happens upon publish. The constraint on parameters is included but not deep behavioral context.

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 a single sentence with no wasted words, front-loading the main action. It is concise, though slightly cryptic with 'PUBLIC https'. Still, it 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?

Despite the existence of an output schema, the description omits important context such as the purpose of the account parameter, the meaning of 'PUBLIC https', prerequisites, and return value details. For a tool with 3 parameters and no schema descriptions, this is insufficient.

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?

With 0% schema description coverage, the description must compensate. It adds the constraint 'Exactly one of image_url / video_url' which clarifies mutual exclusivity, but does not explain the account parameter, default behavior, or format requirements. This provides minimal added meaning 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 states the tool publishes a Story, distinguishing it from sibling tools like publish_image, publish_video, publish_reel, and publish_carousel. It specifies the content type (image or video) and the constraint of exactly one media parameter.

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 implies when to use this tool (for stories, not other post types) but does not explicitly state when not to use it or name alternatives. The 'PUBLIC https' phrase is ambiguous and does not clarify usage context.

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