scrape_channel_authenticated

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions the authenticated session and restricted access but omits prerequisites (e.g., needing to be logged in), potential failures, rate limits, or output behavior common in scraping tools.

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, direct sentence that front-loads the action and the distinguishing feature. It contains no redundant words and earns its place.

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 is concise but leaves gaps regarding when to use this tool among many siblings and what behavioral expectations come with authenticated scraping. With no output schema, a bit more context about the scraping behavior or return format would have improved completeness.

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?

The input schema provides full descriptions for both parameters (url and max_posts), covering 100% of the schema. The tool description adds no parameter-specific details, but since the schema is sufficient, the baseline score of 3 is appropriate.

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 uses a specific verb 'Scrape' with a resource 'Telegram channel' and distinguishes the tool by its authenticated session capability, which differentiates it from sibling tools like scrape_channel. The added note about accessing restricted content clarifies its unique value.

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 implies usage for restricted content requiring authentication, but it does not explicitly state when to use this tool over alternatives or provide exclusions. No mention of prerequisites like prior login is given.

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