telegram-reorder-folders

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

Annotations declare readOnlyHint=false and openWorldHint=true, indicating modification and potential side effects. The description adds the important constraint that all existing custom folder IDs must be included, clarifying a key behavioral aspect. No contradiction with annotations.

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 consists of two sentences: the first defines the purpose, the second adds a critical requirement. No unnecessary words, and the key information is front-loaded.

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?

The description adequately explains the input and its constraint. There is no output schema, so return value is not addressed, but for a simple reordering tool this is acceptable. It would benefit from mentioning that the operation is immediate or that it returns success/failure, but overall it provides sufficient context.

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 single parameter 'order' is documented in the schema with description 'Ordered list of folder IDs (≥ 2). Obtain IDs from telegram-get-chat-folders.' The tool description adds context ('All existing custom folder IDs must be included') that enriches the schema's definition. Schema coverage is 100%, so baseline is 3; the extra context justifies a 4.

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 'Reorder Telegram chat folders' and specifies the action of providing a new order of folder IDs. It distinguishes from siblings like telegram-edit-folder (which edits folder properties) and telegram-create-folder (creates new folders) by focusing solely on 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 requirement: 'All existing custom folder IDs must be included.' This implies the need to first retrieve current folder IDs via telegram-get-chat-folders, giving implicit context. However, it does not explicitly state when to use this tool versus alternatives like telegram-edit-folder for other folder modifications.

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