ads_telegram_account_status

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

No annotations exist, so the description carries the full burden. It usefully enumerates what is inspected (dependencies, credentials, auth state, ignored paths), which implies a read-only diagnostic, but it does not state side-effect-freedom explicitly, nor permissions needed or output shape. Partial disclosure only.

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 with no filler; the enumerated checklist is dense but each item earns its place. Slightly crammed list form is the only minor cost.

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 zero-parameter status tool with no output schema, the description covers the relevant surface of what the check examines. It lacks return-format detail, but that is a minor gap given the tool's simplicity.

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 tool takes zero parameters, so the baseline of 4 applies; the description adds nothing misleading about inputs, consistent with the empty 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?

Specific verb ('Check') plus a concrete resource: local Telegram user-account GramJS/TDLib dependencies, credentials, authentication state, and ignored storage paths. It is clearly a diagnostic/status read, but it never names or contrasts with the closely related sibling ads_telegram_account_auth, so sibling differentiation is left to inference.

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 — check this before attempting authenticated Telegram account operations — but there is no explicit when-to-use/when-not, and the obvious alternative ads_telegram_account_auth is not referenced. An agent can guess its role but is given no routing signal.

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