telegram-report-story

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

Annotations indicate non-read-only and open world. Description explains the multi-step flow, which adds behavioral context beyond annotations. However, it does not disclose side effects, success/failure behavior, or error handling.

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, concise and front-loaded with purpose. Every sentence earns its place with no wasted 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?

No output schema exists, so description should explain response structure to guide the multi-step flow. It mentions using base64 option bytes from previous response but doesn't describe the response format or error behavior. Incomplete for a multi-step tool.

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%. The description adds context for the 'option' parameter (explaining flow), but for other parameters (chatId, ids, message) it adds little beyond schema descriptions. Baseline 3, slight improvement for option explanation.

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?

Clearly states verb 'Report' and resource 'story', and mentions it uses a multi-step option flow. However, title is null and it doesn't explicitly distinguish from sibling report tools like telegram-report-spam, but the context of stories makes it distinct.

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 describes the multi-step process: first call with empty option starts flow, subsequent calls pass option bytes from previous response. Provides clear usage guidance, but does not mention when not to use or alternatives.

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