telegram_unpin_chat_message

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

Since no annotations are provided, the description must carry the full burden. It discloses some behavior (unpins a specific or all messages), but lacks details on side effects, permissions, or error conditions that would be expected for a mutation tool. It does not contradict annotations, so it is not a contradiction, but it is minimal.

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 concise: a one-sentence summary followed by parameter explanations. It is front-loaded with the purpose and uses a clear docstring format that is efficient and well-structured.

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 tool with only 2 optional parameters and an output schema, the description covers the essential information. It explains the two modes of operation and both parameters. However, it lacks potential edge cases (e.g., what happens if message_id is invalid) but these are minor given the tool's simplicity and the output schema.

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 description coverage is 0%, so the description must compensate. It does explain the meaning of message_id ('Identifier of message to unpin. If None, unpins all pinned messages.') and chat_id ('Target chat identifier.'), which adds value beyond the schema's basic type and default info.

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's purpose: 'Unpin a specific message or all messages in a chat.' It uses a specific verb (unpin) with a clear resource (chat message) and distinguishes between two modes (specific vs all), which helps differentiate it from the sibling 'telegram_pin_chat_message'.

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 explains when to use this tool versus alternatives, though not explicitly. It mentions that if message_id is None, it unpins all messages, which guides usage. However, it does not explicitly state when not to use it, but given the sibling list, the purpose is clear.

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