telegram-set-slow-mode

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

The description does not disclose behavioral aspects beyond the annotations. Annotations already indicate it is not read-only and is open-world, but the description does not add context about immediate effects, required permissions, or error conditions. The allowed values are already in the schema.

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 concise with two sentences, front-loads the purpose, and lists allowed values efficiently. 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?

For a simple two-parameter tool, the description adequately explains the concept of slow mode and the allowed values. It lacks mention of who can use this (admin) or potential side effects, but overall sufficient for basic understanding.

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% for both parameters. The description reiterates the allowed values for the 'seconds' parameter, which is already in the schema, adding no new meaning.

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 sets slow mode for a supergroup, specifying the minimum interval between messages. It lists allowed values, distinguishing it from sibling tools like 'set-chat-permissions' or 'set-auto-delete'.

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 explains the purpose and allowed values but does not explicitly state when to use this tool over alternatives, nor does it mention prerequisites like admin permissions or that slow mode applies only to supergroups.

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