ads_telegram_ai_post_reclassify

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

With no annotations, the description carries the full behavioral burden. It valuably discloses that the operation is local-only and never sends or edits Telegram messages, but it does not explain whether reclassification overwrites prior matches/drafts, how idempotent it is, or what permissions/state it requires.

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 tight sentences, front-loaded with the core action and followed by the key safety constraint. No filler or repetition.

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 local rebuild operation with no annotations, no output schema, and an undocumented parameter, the description covers the core action and safety profile but omits scope, side effects, and expected outcome. Adequate but with material gaps.

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 sole parameter project_id has 0% schema description coverage and is not mentioned in the description. The default value 'neron' and the parameter's scoping effect are invisible to an agent unless it inspects the raw 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?

States specific verbs and resources: reclassify saved public Telegram AI posts and rebuild offer matches plus reply drafts. The local-only clause distinguishes it from Telegram send/edit siblings, though it does not name an alternative tool directly.

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 implies this is a local batch rebuild operation that should be used when saved posts need fresh classification/matches. It does not explicitly state when to use it versus post-list, reply-sync, or reply-draft tools, nor does it list prerequisites.

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