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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It adds the result shape (name, category, one-line description, links) and usefully flags that monthly users are reported only 'where measured', i.e. the field is optional. It says nothing about result caps, empty-result behavior, or how the fixed catalogue is kept current.

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 sentences, zero filler, with the purpose and searchable fields front-loaded and the return shape following. Every clause carries distinct information.

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 read-only two-parameter search with no output schema, the description adequately covers what goes in and what comes back, including the caveat that user counts are not always available. The remaining gap is the undocumented 'limit' parameter and the absence of any note on truncation or total match counts.

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 only 50%: 'query' is documented in the schema and the description merely restates the same name/@username/topic forms, while 'limit' (default 10, max 30) is documented nowhere at all. With half the parameters unexplained, the description should have clarified paging/truncation semantics but does not.

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 names a specific verb ('Search') and a precisely bounded corpus ('Catalogue App directory of Telegram mini apps, bots and TON services'), which lets an agent distinguish it from search_channels and search_packs without opening a schema. It stops short of a 5 because it never explicitly acknowledges those siblings or states the exclusion.

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 is only implied: the accepted query forms ('by name, @username or topic') suggest how to call it, but there is no statement of when to prefer this over search_channels/search_packs, no prerequisites, and no guidance on broadening or narrowing a query that returns nothing.

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