ads_telegram_chat_mark_read

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

With no annotations, the description carries the behavioral burden and does well: it discloses that no message is sent, no local dialogue row is created, and bots/channels are not affected. It does not discuss permissions or the exact read-state response, but it covers the key non-effects and confirmation requirement.

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?

The description is compact and front-loaded, leading with the core action and immediately adding the confirm requirement and key exclusions. Every clause carries useful 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 simple two-parameter action with full schema coverage and no output schema, the description supplies the necessary scope, confirmation requirement, and side-effect exclusions. Nothing important for correct invocation appears to be missing.

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 100%, so both parameters are already well documented by the schema. The description reinforces the confirm requirement but adds little beyond the schema's own descriptions of chat and confirm.

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 states a specific verb and resource: marking a human one-to-one Telegram chat as read. It also narrows scope by excluding bots and channels, which helps distinguish it from sibling Telegram tools such as ads_telegram_chat_reply and ads_telegram_account_send.

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?

It gives clear usage context and exclusions: requires confirm=true and does not apply to bots or channels. However, it does not explicitly name an alternative tool for marking other chat types as read, so it falls short of full when-to-use/when-not guidance.

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