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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety and determinism profile is fully covered structurally. The description adds little beyond that: "ChatGPT deep-research compatible" is unelaborated jargon that doesn't tell the agent anything actionable about result shape, ranking, or limits. With an output schema present, the return-format gap is partly excused, so a 3 is fair.

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 compact clauses with the core action front-loaded and the routing hint second, which is the right ordering. The one weak sentence is "ChatGPT deep-research compatible," which spends words without conveying verifiable information to the agent.

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 single-parameter read tool with full annotation coverage and an output schema, the description covers what to search, what entities are in scope, and where to go for aggregate stats. The remaining ambiguity is minor and largely absorbed by the structured fields.

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?

There is a single parameter with 100% schema description coverage ("Search query, any language"), so the schema already carries the meaning. The description adds no syntax, matching behavior, or query-construction guidance beyond what the schema states, making this the baseline case rather than an enhancement.

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?

Specific verb ("Search") plus resource ("tgden Telegram catalog") with the entity types enumerated in parentheses, so the agent knows what universe is being searched. It partially differentiates from siblings by naming search_telegram as the route for counts/categories/trust scores, but does not contrast with search_posts or fetch, which also sound like content retrieval.

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?

Explicitly routes one class of need away from this tool: "for counts, categories and trust scores use search_telegram," which is a concrete condition that selects an alternative. There is no exclusion guidance against search_posts, fetch, or best_channels_by_category, so sibling selection is only partially resolved.

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