Pin Message to Top of Chat

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

With annotations already indicating readOnlyHint=false and idempotentHint=true, the description adds valuable operational context: it is a mutation, requires a specific environment flag, and needs admin permissions in certain contexts. It does not mention error behavior or pin limits, but that is not a required disclosure given the existing annotations.

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?

Three short, focused sentences with no filler. The action is front-loaded, the mutation and prerequisites come second, and the unpin alternative is provided last. Every sentence earns its place.

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 output schema exists and the annotations cover safety/idempotency, the description supplies the remaining essentials: purpose, prerequisites, and the undo path. An agent can decide whether to call the tool and how to avoid common permission and configuration failures.

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 100%, so the parameters are already fully documented in the schema. The description adds minimal parameter-level meaning beyond confirming the chat/supergroup context, which matches the baseline for high schema 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 states a specific action ('Pin a message to the top'), identifies the target resource ('chat or supergroup'), and explains the intent ('for high visibility'). It is clearly distinct from siblings like unpin_message, delete_message, and send_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 explicitly names the operation type as a mutation and gives concrete preconditions: TELEGRAM_SEND_ENABLED=true and admin permissions in supergroups/channels. It also directs the agent to unpin_message when the goal is to remove a pin, which is explicit alternative guidance.

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