telegram-set-admin

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

The description correctly indicates a write operation ('promote') consistent with readOnlyHint=false. However, it does not detail the scope of 'full permissions' or side effects, leaving some ambiguity. Annotations already provide the basic behavioral hint.

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 a single sentence that conveys the core functionality without wasted words. It could be slightly improved with front-loaded structure, but it is efficient.

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 lack of output schema and minimal annotations, the description fails to explain what 'full permissions' entails, that the tool only works on supergroups/channels, or how the optional title parameter affects behavior. More context is needed for correct invocation.

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 input schema already provides descriptions for all parameters (e.g., 'Chat ID or username'), and the description does not add further semantic context beyond what is in the schema.

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 verb 'promote' and resource 'user to admin in a supergroup or channel with full permissions', which distinguishes it from siblings like 'remove-admin' and 'set-chat-permissions'.

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 provides no guidance on when to use this tool versus alternatives, such as 'set-chat-permissions' or 'remove-admin', nor does it mention prerequisites or conditions.

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