ads_telegram_ai_chat_upsert

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

With no annotations, the description carries the full burden but does add real value: it discloses that the write is local-metadata-only and that no participants are collected and no messages are sent. It omits upsert conflict semantics (which fields are overwritten vs merged on an existing chat), permission/auth needs, and idempotency key behavior — significant gaps for a 14-parameter mutation tool.

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 action and scope, followed by the one safety constraint that matters. Nothing is redundant relative to the name or schema.

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 14-parameter write tool with no annotations, no output schema, and 0% schema documentation, the description is far too thin — an agent cannot determine what an upsert will overwrite, what a success response looks like, or how to populate most 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?

Schema description coverage is 0% across 14 parameters, so the description must compensate and largely does not. It only loosely hints at project_id ("under a project") and topic_hits/chat_type via "AI-related topics" and "group/channel"; enums like status, the meaning of relevance_score, discovery_queries, and the distinction between first_seen_at and last_scanned_at are left entirely unexplained.

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 a specific verb+resource: "Save or update one public Telegram group/channel" record, scoped to AI-related discovery. The singular "one" and "upsert" framing clearly distinguish it from the plural read tool ads_telegram_ai_chat_list, though no sibling is named explicitly.

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 implied rather than stated: you use it when you have discovered a public chat and want to persist it. The negative clause ("never collects participants or sends messages") implicitly rules out the messaging siblings like ads_telegram_channel_direct_send, but no explicit when/when-not or prerequisite guidance is given.

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