Delete a story from a Telegram business account using its business connection ID and story ID to remove unwanted or outdated content.
Delete a story (v9.0).
| Name | Required | Description | Default |
|---|---|---|---|
| story_id | Yes | ||
| business_connection_id | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description merely repeats the tool's name and adds a version tag. It does not disclose any behavioral traits beyond the annotations, such as irreversibility or required business connection.
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 phrase 'Delete a story' is succinct and front-loaded. However, the parenthetical '(v9.0)' adds no informational value and slightly detracts from conciseness.
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 lack of output schema and minimal description, the tool is under-specified. It does not explain the effect of deletion, error conditions, or relationship to business accounts, making it incomplete for an agent to invoke correctly.
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 has 0% description coverage, and the description provides no explanation of story_id or business_connection_id. The agent is left without semantic guidance for these required parameters.
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 a specific action ('Delete') on a specific resource ('a story'), which distinguishes it from sibling tools like edit_story or repost_story. It is direct and unambiguous.
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?
No guidance is provided on when to use this tool versus alternatives, such as delete_message or delete_business_messages. The description lacks context about prerequisites, ownership, or scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.