deleteStory

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

With no annotations provided, the description carries the full burden, and it does a solid job: it discloses the required permission (can_manage_stories), limits the operation to bot-posted stories, and states the success return value (True). It does not cover failure behavior or irreversibility in depth, but 'Deletes' already signals destructive intent.

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 sentences with no filler: the main action is front-loaded, followed by the permission requirement and the return value. Every sentence earns its place, and the entire definition can be processed quickly.

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 low-complexity, two-parameter delete operation with no output schema, the description covers the action, scope, authorization, and success response. The only meaningful gap is failure semantics (e.g., what happens when the story does not exist), which is a minor omission given how direct the operation is.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema's generic 'unique identifier' phrasing. It clarifies that story_id refers to a bot-posted story and that business_connection_id belongs to a managed business account, which helps an agent map the parameters correctly.

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 names a specific verb ('Deletes') and a precise resource ('a story previously posted by the bot on behalf of a managed business account'), which clearly separates it from sibling tools like deleteMessage, deleteBusinessMessages, or editStory. Adding the permission requirement further pins down its scope.

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 clear context for when the tool applies: the story must be one previously posted by the bot, the account must be a managed business account, and the can_manage_stories bot right is required. It names no explicit alternatives or exclusion cases, but the conditions given are specific enough for an agent to select this tool correctly.

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