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

With no annotations, the description carries the burden of behavioral disclosure and does so well: it explains filtering by type, category, language, and limit, and provides defaults, allowed values, and the numeric range for limit. It does not mention auth, rate limits, or error behavior, but for a read-only list operation these are less critical.

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 opens with a clear one-sentence summary and then uses a compact Args block. Every line adds useful information and there is no redundant or verbose content.

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?

All four optional parameters are fully documented with types, defaults, allowed values, and constraints. The description also connects to a sibling tool for category slugs, and since an output schema exists, the lack of return-format details is not a gap. The tool is simple enough that this description is sufficient 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?

Schema description coverage is 0%, so the description must fully document parameters, and it does. Each parameter receives its allowed values or format: type lists all five options, category provides an example and source, lang enumerates supported languages, and limit specifies the 1-25 range with default.

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 identifies the tool as returning 'the most-followed Telegram resources' with an optional category filter. It does not use an explicit verb like 'list', but the meaning is unambiguous and the sibling tools (search, get single resource, list categories) are clearly distinct in scope.

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?

Usage context is implied through parameter guidance such as 'Optional category slug' and the cross-reference to list_telegram_categories for valid category values. However, it does not explicitly state when to prefer this tool over search_telegram or get_telegram_resource, leaving some routing decisions to the agent.

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