telegram-toggle-prehistory-hidden

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

Annotations indicate non-readonly (mutation). The description adds specific behavioral context: 'When hidden=true, new joiners cannot see messages posted before they joined'. This explains the effect beyond the annotation's binary read-only hint.

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 sentences, efficient and front-loaded. Every sentence earns its place, with no wasted words. The purpose and key constraints are immediately clear.

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?

The description covers the tool's purpose, effect, and constraints. Given the tool's simplicity and the presence of annotations (readOnlyHint, openWorldHint), the description is sufficiently complete. No output schema expected, so return value details are unnecessary.

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%, so baseline is 3. The description implicitly references the 'hidden' parameter by stating 'When hidden=true', but does not add additional meaning beyond the schema descriptions. No new param insights provided.

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 verb 'Toggle' and the resource 'pre-history visibility for new members in a supergroup'. The constraint 'Supergroup only; requires admin' distinguishes it from other toggle tools in the sibling list.

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 (supergroup admin wanting to control pre-history visibility) and states constraints (supergroup only, requires admin). It does not explicitly mention when not to use or list alternatives, but the constraints offer clear guidance.

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