Publish story

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

Annotations already communicate readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds the story-specific platform context, but does not disclose further behavior such as whether the post is published immediately, status changes, or side effects. No contradiction with annotations.

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 only two short sentences, front-loading the core purpose ('Publish a post as a story') before adding a usage hint. The second sentence is partly redundant with the first, but it does earn its place by explicitly stating when to use the tool.

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?

Given the tool's low complexity, two fully documented parameters, and annotations covering the safety profile, the description provides enough context for an agent to invoke it correctly. It does not explain return values or prerequisites, but these are less critical for a simple publish action.

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 input schema fully documents both parameters (postId and platform) with 100% coverage, including the enum for platform. The description's mention of 'Facebook or Instagram' merely restates the schema and adds no extra parameter-level meaning, so the baseline 3 applies.

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') and resource ('a post as a story on Facebook or Instagram'), making the tool's function immediately clear. It also naturally distinguishes from sibling tools like publish_post by focusing on the story format and platforms.

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 second sentence explicitly says 'Use this when the user wants to post an Instagram/Facebook story,' giving a clear trigger condition for selecting the tool. However, it does not mention alternatives or when not to use it, so it stops short of full routing guidance.

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