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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description's added value is the privacy/scope boundary around Telegram Business conversations and message sending. It does not disclose the aggregation scope (all channels? whole workspace?), freshness of the check, or how issues are grouped, which matters for an audit-style call with an output schema.

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?

A single front-loaded sentence beginning with the trigger condition, with the exclusion trailing. No filler or repetition. It is arguably too terse given the behavioral gaps it leaves, but structurally sound.

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?

Output schema exists so return values need not be explained, and annotations cover safety, making the definition minimally sufficient for invocation. The missing piece is which content universe is scanned and when to prefer this over search_post_drafts for finding problematic drafts, which leaves the agent to guess about scope.

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?

With 100% schema description coverage on the single optional 'locale' enum, the baseline is 3. The description says nothing about locale influence (e.g. whether it changes issue wording or filtering), so it adds no meaning beyond the schema.

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 enumerates the problem categories the tool surfaces (unfinished drafts, formatting/media problems, lost permissions, failed deliveries, publication-target gaps), which implies an issue-audit resource. However, it never states a concrete verb+resource ('returns a list of posts needing attention') and the name alone doesn't disambiguate it from siblings like search_post_drafts or get_post. Purpose is inferable but not stated.

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?

Opens with an explicit 'Use when reviewing...' trigger covering the specific situations that select this tool, which no sibling covers. It also gives an exclusion ('Does not read private Telegram Business conversations or send messages'), though that exclusion reads as a scope disclaimer rather than routing to a named alternative. No sibling is named as an alternative, so it stops short of 5.

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