telegram-set-privacy

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and has open-world effects. The description adds context by listing the settings it modifies, but it does not disclose potential side effects, authorization requirements, or whether changes are reversible. The description and annotations are consistent.

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 a single, concise sentence that captures the essence of the tool without extraneous words. It is well-structured and front-loaded with the core action.

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?

Given no output schema, the description does not explain return values or confirmation. It covers the tool's purpose but misses details on how the parameters interact (e.g., relationship between rule and allowUsers/disallowUsers). It is adequate but not thorough for a tool with four parameters, including array types.

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 schema has 100% description coverage for all parameters, so the description does not need to add parameter details. It provides a general overview of the tool's purpose, which is consistent with the schema. No additional semantics beyond what the schema offers.

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 clearly states the tool configures privacy settings for a Telegram account, listing examples like phone number and last seen. It is specific enough to distinguish from general account settings, though it does not explicitly differentiate from the sibling 'telegram-set-global-privacy-settings'.

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 the tool is for visibility controls, but it lacks explicit guidance on when to use this tool versus alternatives like 'telegram-set-global-privacy-settings' or read-only tools like 'telegram-get-global-privacy-settings'. No exclusions or prerequisites are mentioned.

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