Delete contacts

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

Annotations already mark this as not read-only and open-world, so the mutation type is known. The description adds useful behavioral context by explaining that the account 'stays subscribed to nothing new' and 'only forgets the saved contact entry,' which clarifies the scope of deletion beyond simple mutation hints.

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 three short sentences with the core action front-loaded. The final sentence explains scope without unnecessary repetition or filler.

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 one-parameter mutation tool with no output schema, the definition covers the important semantic boundaries: what is removed, what is not changed, and that multiple identifiers are allowed. It could be slightly stronger if it explicitly stated irreversibility or expected confirmation behavior, but the core context is present.

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 single parameter is already documented. The description still adds meaning by listing accepted identifier formats ('@username, user id, or numeric id') and confirming that several contacts may be passed at once, which goes slightly beyond the schema's brief parameter note.

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 and resource ('Remove saved contacts') and explicitly distinguishes the tool from its inverse, telegram_add_contact. It also clarifies that multiple contacts may be removed in one call, so an agent can identify the operation without opening the schema.

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?

It gives clear context by naming the inverse operation and noting batch removal, which helps route between adding and deleting contacts. However, it does not explicitly address when to use this instead of related actions like telegram_block_user, nor does it state when this tool should not be used.

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