telegram-get-peer-stories

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

Discloses that no raw media blobs are returned, only compact metadata with fields like id, date, expireDate, caption, mediaType, counters. Aligns with readOnlyHint and openWorldHint annotations without contradiction.

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 concise sentences with front-loaded purpose. No wasted words; each sentence adds essential information about behavior and alternatives.

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?

With one parameter and no output schema, description sufficiently explains input and output (metadata fields) and cross-references sibling tool for media download. Complete for its complexity.

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 has 100% coverage for 'chat' parameter, but description adds value by listing acceptable identifier formats (id, @username, phone, display name fragment), aiding agent understanding beyond the schema description.

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 'Fetch currently active stories posted by a specific peer (user/channel)', using a specific verb and resource. It distinguishes from siblings like 'telegram-get-all-stories' and 'telegram-get-stories-by-id' by specifying 'by a specific peer'.

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?

Explicitly notes that it returns only metadata and no raw media blobs, directing users to 'telegram-download-media' for media bytes. Also implies this is a read operation, consistent with readOnlyHint annotation.

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