telegram-search-sticker-sets

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety and external search. The description adds only that it returns 'matching sticker pack names' but does not elaborate on pagination, limits, or handling of no results. No additional behavioral details are provided beyond 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 is a single, well-structured sentence that efficiently conveys the purpose and links to a related tool. Every word earns its place with no redundancy or fluff.

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 search tool with no output schema, the description adequately explains the return value ('matching sticker pack names') and provides a usage hint. It is complete for the tool's complexity, though it could optionally mention fuzzy matching or case sensitivity.

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 100% for the single parameter 'query', which includes examples. The tool description reinforces that the query searches by 'name or keyword', but adds no new syntax or format details beyond the schema. Given high coverage, baseline 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 clearly states the action ('search'), the resource ('sticker sets'), and the input type ('by name or keyword'). It also mentions the output (matching sticker pack names) and references a sibling tool for further use, distinguishing it from related tools like telegram-get-installed-stickers.

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 implicitly suggests usage for discovery before using telegram-get-sticker-set, but does not explicitly state when to prefer this tool over alternatives (e.g., telegram-get-installed-stickers, telegram-search-global). No explicit exclusions or conditions are provided.

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