telegram-activate-stealth-mode

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

Annotations indicate mutation (readOnlyHint=false) and open-world effects (openWorldHint=true). The description adds important behavioral details: the Premium requirement and the specific timeframes for future mode (25 minutes). However, it does not explain if the effect is reversible or how long past mode changes last.

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 highly concise: two sentences covering the core action, parameters, and a key constraint (Premium). Every sentence earns its place with no unnecessary words.

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 mutation tool with two booleans and no output schema, the description covers the main functionality and an important error condition. Minor gaps exist around permanence and future mode toggling, but overall it is sufficiently complete 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?

Schema coverage is 100% with clear parameter descriptions, so baseline is 3. The tool description restates the parameter purposes in plain language but does not add significant semantic value beyond what the schema already provides.

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?

Description clearly states the tool hides story views, specifying two modes (retroactively for past views and for the next 25 minutes for future views). It also mentions the Premium requirement, which distinguishes it from many other story-related sibling tools that handle sending, deleting, or reading stories.

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 context for when to use the tool (to hide story views) but does not explicitly mention when not to use it or compare it to alternatives like privacy settings or other story tools. No exclusions or alternatives are given.

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