telegram_pin_message

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

Annotations already provide idempotentHint=true and non-destructive/non-read-only hints. The description adds context about requiring admin permissions and the return format (JSON with success/error), which goes beyond annotations without contradiction.

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 short and efficient: two sentences plus a clear Args/Returns section. It front-loads the purpose and avoids unnecessary details, making it easy to scan.

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 simple nature of pinning a message, the description, annotations, and schema together provide everything needed: purpose, prerequisites, parameters with descriptions, return format, and idempotency. No gaps.

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?

The input schema already includes detailed descriptions for each parameter (e.g., 'Message ID to pin', 'Pin silently without notification'). The tool description merely lists the parameter names and types without adding new semantic information, so it adds minimal value beyond the schema.

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 'Pin a message in a chat' with a specific verb and resource, and distinguishes it from siblings like send/delete/forward. It also includes the prerequisite that the bot must be an admin with pin_messages permission.

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 states the prerequisite (bot must be admin with pin_messages permission), giving a clear condition for use. However, it does not directly contrast with sibling tools or provide when-not-to-use guidance.

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