telegram-get-all-stories

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

Annotations indicate readOnlyHint and openWorldHint as true, and the description adds that non-raw media data is returned. It also details pagination behavior and the hidden parameter, which goes beyond annotations without contradicting them.

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 paragraph that efficiently covers purpose, pagination, hidden option, and output summary. Every sentence adds value and it is appropriately front-loaded.

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?

Despite no output schema, the description specifies the returned metadata fields (id, date, expireDate, caption, mediaType, counters), which is sufficient for an agent to understand the tool's output. It covers the essential aspects needed for correct usage.

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 parameter descriptions. The description adds valuable context for 'next' and 'state' (e.g., 'pass the returned state back') and explains the effect of 'hidden', enhancing understanding 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 the action: 'Fetch active stories from contacts/channels the user follows.' This is a specific verb-resource pair that distinguishes it from sibling tools like telegram-get-peer-stories (stories for specific peers) and telegram-get-stories-by-id (by ID).

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 explains pagination using 'next' and 'state', and when to use 'hidden:true' for muted/archived peers. It provides clear guidance on how to use the tool but does not explicitly cover when not to use it or contrast with alternatives, though the context is adequate.

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