tgtrack_delete_invite_link

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

With no annotations, the description carries the full burden. It discloses irreversibility and the need for confirm, which are critical behavioral traits. It does not detail success responses or error conditions, but the disclosed traits are sufficient for basic safe usage.

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, direct sentence with no filler. The emoji effectively highlights the destructive nature. Every word adds value, achieving maximum 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 no output schema and no annotations, the description is adequate for a simple irreversible delete action. However, it lacks details on return values, error handling, and resource identification (chatID, linkID), which could be clarified for completeness.

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 0%, so the description must compensate. It explains the confirm parameter (requires true), but provides no meaning for chatID or linkID. This partial coverage partially compensates but not fully for all three 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 the tool deletes an invite link/integration and is irreversible. The verb 'delete' and noun 'invite-link/интеграцию' specify the action and resource, distinguishing it from sibling tools like tgtrack_create_integration (create) and tgtrack_delete_outbound_link (different resource).

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 explicitly requires confirm:true to execute, providing a prerequisite. However, it does not specify when to use this tool versus similar deletion tools or when not to use it, leaving usage context implicit.

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