telegram_publish_message

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

Annotations indicate a write/non-idempotent operation, but the description adds valuable context: bot admin requirement, parse_mode formatting behavior, effects of disable_web_page_preview and disable_notification, and response format differences. No contradictions with 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?

The description is well-structured with an intro, usage note, Args section, and Returns section. Every sentence adds value, and there is no redundancy or fluff. It is appropriately sized for a 6-parameter tool.

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?

The tool is moderately complex and the schema provides no descriptions, yet the description covers purpose, prerequisites, every parameter, defaults, and return values. This makes the tool fully invocable without external documentation.

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%, but the description thoroughly explains all 6 parameters, including types, options, defaults, and the meaning of channel_id formats. This fully compensates for the schema gaps.

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 first sentence clearly states the verb and resource: 'Publish a message to a Telegram channel.' It distinguishes from sibling tools like telegram_publish_photo by focusing on text messages and explicitly says 'post new messages.'

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 clearly states when to use the tool ('Use this tool to post new messages to a Telegram channel where the bot is an admin') and gives a prerequisite (bot must have permission). It does not explicitly mention alternatives (e.g., for photos use telegram_publish_photo), but the context is clear enough.

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