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, so the description is not required to cover safety. It adds value by specifying that the output is 'matching sticker pack names', which is useful given the lack of an output schema. It does not mention any limits or search behavior, but overall it complements the annotations well.

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, clear sentence that is front-loaded with the action. Every word serves a purpose, making it highly concise and efficient.

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 tool with one parameter and no output schema, the description covers the main aspects: what it does, how to use the query parameter, and how the results relate to another tool. It could be slightly more complete by mentioning possible no-result behavior or pagination, but it is sufficient for the tool's simplicity.

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 has 100% description coverage, and the tool description essentially repeats the purpose. It does not add new semantic meaning beyond what is in the schema, such as search syntax or result quality. 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 clearly states the verb 'Search' and the resource 'sticker sets', and it distinguishes itself from sibling tools by noting that the results are used with 'telegram-get-sticker-set'. This differentiation is effective and specific.

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 clear context by linking to 'telegram-get-sticker-set', implying a workflow. However, it does not explicitly state when to use this tool versus alternatives like 'telegram-get-installed-stickers' or 'telegram-get-recent-stickers', which could help an agent make better decisions.

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