telegram-set-global-privacy-settings

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

The description discloses partial update behavior and Premium requirements for specific fields, adding context beyond the readOnlyHint=false annotation. It does not mention side effects or return values, but given no output schema, this is acceptable.

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 clear, front-loaded sentences with no extraneous information. First sentence states action and scope, second gives usage guidance and special requirements.

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 boolean update tool with a get counterpart, the description covers how to use (partial update) and special requirements. Adequate for an agent to invoke correctly.

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% with each parameter having a description. The tool description adds operational guidance: partial update semantics and Premium requirements, which goes beyond the 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?

The description clearly states it updates account-level global privacy settings, using specific verb 'Update' and resource 'account-level global privacy settings'. It distinguishes from sibling tools like telegram-get-global-privacy-settings and other set-* tools.

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 provides explicit usage guideline: 'Only pass the fields you want to change — omitted fields keep their current values.' It also notes Premium requirements for two fields. However, it does not explicitly mention when to use this vs alternatives like getting current settings first.

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