Edit a group or channel

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds real behavioral context beyond that: admin permission requirement with the failure mode (Telegram refuses), and idempotent-ish partial update semantics where omitted fields are untouched. It does not describe the response payload, but that is minor for this 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?

Four short sentences, front-loaded with what it changes, then permissions, then update semantics, then limits. Every sentence carries actionable information with no filler.

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?

Covers purpose, permissions, partial-update semantics, and field constraints, which is sufficient for a 3-parameter mutation with no output schema. Only the 'chat' identifier format (username vs numeric id) is unaddressed.

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 0%, so the description must compensate, and it does: title bounded at 1-128 chars and about bounded at up to 255, matching the schema's minLength/maxLength. The 'chat' identifier parameter is left implicit, which is the only real gap.

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?

States a specific verb and resource: 'Change a group/channel title and/or description.' This is clearly distinguishable from sibling mutations like telegram_set_chat_photo, telegram_edit_message, or telegram_update_profile, which target different resources.

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?

Gives clear context ('Needs admin rights; Telegram refuses otherwise') and states partial-update behavior ('Omit a field to leave it untouched'). It does not name an explicit alternative tool or a when-not-to-use condition, so it stops short of a 5.

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