telegram-get-suggested-folders

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

The description adds context about returning folder templates, but annotations (readOnlyHint: true, openWorldHint: true) already cover the read-only nature and potential unknown data. No contradictions or extra behavioral details beyond what annotations imply.

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?

Two efficient sentences: first states the action with examples, second explains output and links to a related tool. No unnecessary words, front-loaded with key info.

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 no input parameters and no output schema, the description fully covers what the tool does and what it returns. It is complete for a simple read-only tool.

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?

With no parameters and 100% schema coverage, the description effectively explains the tool's purpose and output. It adds meaning beyond the empty schema by describing the returned data (folder templates).

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 retrieves suggested chat folders, provides examples like 'Unread, Personal, Work', and distinguishes from siblings by mentioning it returns templates for creating folders with 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 implies the tool is for viewing suggested folders before creation and references telegram-create-folder. While it doesn't explicitly state when not to use it or compare to alternatives like telegram-get-chat-folders, the context is clear.

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