telegram-set-business-away

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

Annotations indicate mutability and open-world side effects. Description adds that it uses a quick reply shortcut as template, and clear=true disables it. No 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?

Three concise sentences front-loaded with purpose, no unnecessary words.

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?

With 9 parameters and no output schema, description covers main behavior and prerequisites. Lacks detail on return value but sufficient for selection.

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 coverage is high (78%), so baseline of 3. Description only mentions clear=true and shortcut template; schema already documents all parameters well.

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?

Description clearly states the tool sets a Telegram Business away message for auto-reply when offline or outside work hours. It distinguishes from siblings like telegram-set-business-greeting and telegram-set-business-intro.

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?

Offers clear guidance: requires Business subscription, how to disable with clear=true, and context for use. Could be improved by explicitly stating when not to use, but adequate.

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