telegram-reorder-folders

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

The description discloses mutation (reorder) and the constraint about including all custom folder IDs. However, it does not mention potential side effects (e.g., impact on system folders), error conditions for missing IDs, or whether the change is immediate. Annotations indicate openWorldHint=true, so additional context about external effects would be beneficial.

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 with no unnecessary words. It front-loads the action and follows with the critical constraint. Every sentence serves a purpose.

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 there is no output schema, the description does not explain what the tool returns (e.g., success indication, updated order). It also lacks details on idempotency, reversibility, or confirmation. For a simple reorder, this may be sufficient, but more completeness would enhance clarity.

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 schema covers the single parameter 'order' with full coverage (100%). The description adds value by specifying that IDs come from telegram-get-chat-folders and that all existing custom folder IDs must be included, which is not in the schema. This goes beyond the baseline of 3.

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 (Reorder), resource (Telegram chat folders), and a key constraint (all existing custom folder IDs must be included). This distinguishes it from siblings like telegram-edit-folder (which modifies individual folder properties) and telegram-create-folder.

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 an important requirement (all existing custom folder IDs must be included) and implicitly suggests using telegram-get-chat-folders to obtain IDs. However, it does not explicitly guide when to use this tool versus alternatives (e.g., when to use telegram-edit-folder instead) 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.