scrape_group

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

No annotations are provided, so the description carries the full burden. It does disclose that posts are returned in markdown format and that it uses an authenticated session if logged in, which is useful. However, it omits other behavioral traits such as whether login is required, failure behavior without a session, or read-only nature, leaving significant gaps.

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 two sentences long, directly states the action and output format, and contains no redundant or irrelevant information. It is appropriately front-loaded and concise.

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 tool has only two parameters, but it sits among many related scraping tools with no differentiation. The description does not explain when to use this tool versus siblings, nor does it cover authentication failure scenarios. For a tool with no annotations or output schema, this leaves important context missing.

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 already documents both parameters (url and max_posts) with descriptions, achieving 100% coverage. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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 the verb 'Scrape' with resource 'Telegram group' and specifies output as 'posts in markdown format', making the core function clear. However, it does not explicitly distinguish from sibling tools like scrape_channel or scrape_channel_authenticated beyond the word 'group', so it is clear but lacks explicit differentiation.

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 no guidance on when to use this tool versus alternatives like scrape_channel, scrape_channel_full, or scrape_manual. The only contextual hint is 'Uses authenticated session if logged in', which implies auth behavior but does not explain selection criteria.

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