send_telegram_notification

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

No annotations are provided, so the description must carry transparency on its own. It usefully clarifies that media requires either url or base64Data and that text can serve as a caption, but it doesn't disclose error handling, delivery guarantees, or return behavior, leaving gaps.

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 four short sentences, with the core purpose in the first sentence. Every sentence adds information about capabilities or constraints, with no filler or redundancy.

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 description adequately covers what content can be sent and the media constraint, but it omits any mention of parseMode, disableNotification, or the tool's return value. Given the tool has a nested media object and no output schema, these omissions leave it less complete than ideal.

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 schema already documents the media subfields and the message-as-caption behavior. The description adds the combination rules (text only, media only, or media+caption) but doesn't clarify parseMode or disableNotification, which remain undocumented in both schema and description.

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 opens with 'Send a notification to the configured Telegram chat,' clearly identifying the action and target. It distinguishes itself from siblings like telegram_send_and_wait_reply by emphasizing 'notification' rather than interactive reply.

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 outlines supported content types and the media/text combinations, providing clear context for when to use it. However, it doesn't explicitly reference sibling tools or state when not to use it (e.g., when a reply is needed), leaving some usage guidance implicit.

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