telegram-delete-business-chat-link

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

Annotations indicate readOnlyHint=false (write operation) and openWorldHint=true (side effects possible). The description adds the subscription requirement but does not disclose additional behavioral traits like irreversibility, immediate invalidation of link, or any cascading effects. With annotations providing partial transparency, the description adds modest context but not enough for a higher score.

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: first states action and method, second adds requirement. Extremely concise with no extraneous information. Front-loaded with the core purpose.

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 simple delete operation with one parameter, the description is mostly complete. It lacks mention of return value or success behavior, but given no output schema, this is a minor gap. The openWorldHint annotation suggests side effects, which are not explained, keeping it from a 5.

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% and describes the 'slug' parameter with format hint. The description reuses 'by its slug', adding no new semantic depth beyond the schema. Baseline 3 for high coverage.

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 action (delete), resource (Telegram Business chat link), method (by slug), and a prerequisite (requires Telegram Business subscription). It distinguishes from sibling tools like create-business-chat-link, edit-business-chat-link, and get-business-chat-links.

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 a clear prerequisite (Telegram Business subscription) and context (by slug), but does not explicitly state when not to use this tool or name alternative tools. However, given the specific delete action, the usage is reasonably implied.

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