telegram-set-business-greeting

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

The description adds behavioral information beyond annotations: it requires a subscription and can clear the greeting. Annotations already indicate this is a write operation (readOnlyHint=false). The description does not cover potential side effects or limits, but the combination is adequate for a mutation tool.

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 exceptionally concise: two sentences that front-load the purpose, include key constraints (subscription), and a special flag (clear). No unnecessary words or repetitions.

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 moderate complexity (6 parameters all well-documented in schema, no output schema, annotations present), the description covers the main intent and constraints. It lacks details about overriding existing greetings or interaction with quick replies, but overall it's complete enough for an agent.

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 schema already explains all parameters. The description adds minimal extra meaning by mentioning 'quick reply shortcut as template' and 'auto-reply to new conversations', which contextualizes shortcutId and audience, but not enough to exceed the baseline.

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: setting a Telegram Business greeting message, which is an auto-reply sent to new conversations using a quick reply shortcut. It distinguishes from sibling tools like telegram-set-business-away and telegram-set-business-intro by specifying it's for greetings.

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 mentions the requirement of a Telegram Business subscription and the clear flag to disable, providing context for usage. However, it does not explicitly compare to other business setting tools or state when not to use, but the context is sufficient for an agent to infer appropriate use.

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