telegram-reorder-folders

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

Annotations indicate readOnlyHint=false and openWorldHint=true. The description adds that all custom folder IDs must be included, but does not disclose what happens if an ID is missing, whether system folders are affected, or error behaviors. With annotations covering part of the transparency burden, this is adequate but not thorough.

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 two sentences, no wasted words, and front-loaded with the action. Every sentence adds value.

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 mutation tool with annotations, the description covers the main requirement but lacks details on success response, error handling, or side effects beyond the constraint. Adequate but could be more complete given no output schema.

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 100%, so the description does not need to add much. The description does not add new meaning beyond the schema's parameter description, which includes 'Obtain IDs from telegram-get-chat-folders.' Baseline 3 is appropriate.

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 reorders Telegram chat folders by taking a new order of folder IDs. It distinguishes from siblings like telegram-create-folder, telegram-delete-folder, and telegram-edit-folder by specifying the action of reordering.

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 a clear constraint: 'All existing custom folder IDs must be included.' This guides usage, but does not explicitly state when to use this tool versus alternatives like telegram-edit-folder or when not to use it.

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