telegram-toggle-folder-tags

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

Annotations already indicate readOnlyHint=false (mutation) and openWorldHint=true (potential side effects). The description adds that Telegram Premium is required, which is useful but does not elaborate on behavioral traits like immediate effect, reversibility, or rate limits. This is adequate given the simple nature of the 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?

The description is two sentences, front-loading the action and explanation, followed by the prerequisite. No extraneous words; every sentence earns its place.

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 boolean toggle with no output schema, the description is complete. It explains the function, provides a prerequisite, and the single parameter is fully documented in the schema. No additional 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 covers 100% of parameters with clear descriptions: 'true to enable folder tags, false to disable'. The description adds no further parameter-level meaning beyond the schema, so the baseline score of 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 uses specific verbs ('enable or disable') and identifies the resource ('folder tags'), with an explanatory parenthetical about what folder tags are. It clearly distinguishes from sibling tools like telegram-create-folder or telegram-edit-folder by focusing on the tags toggle action.

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 states 'Requires Telegram Premium,' providing a clear prerequisite. However, it does not explicitly discuss when to use the tool vs alternatives or when not to use it. Since there is no direct alternative tool for this action, the guideline is adequate but lacks explicit contextual boundaries.

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