scrape_date_range

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions 'Uses authenticated session if logged in', which is useful, but it doesn't explain the behavior when not logged in, what happens with private channels, rate limits, or the return structure. This is minimal disclosure for a scraping tool that may have significant side effects or constraints.

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 concise sentences with no redundancy. The first sentence front-loads the primary function, and the second adds relevant authentication context. Every word 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 tool lacks annotations and an output schema, so the description must compensate. It does not clarify whether date_to is optional and what happens if omitted, what the output format is, or how it interacts with sibling tools. This leaves significant gaps for an agent to correctly invoke and interpret the 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?

The input schema already provides 100% coverage with clear descriptions for all three parameters (url, date_from, date_to, including format examples). The tool description adds no additional parameter-level meaning beyond restating the date-range concept, so the baseline 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 clearly states the tool scrapes posts within a specified date range, using a specific verb ('scrape') and resource ('posts'). This distinctly differentiates it from sibling tools that scrape entire channels/groups without date filtering (e.g., scrape_channel, scrape_channel_full).

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 scraping posts in a date range but provides no explicit guidance on when to choose it over alternatives like scrape_channel_full or scrape_manual. It also doesn't mention prerequisites such as login requirements for private channels, leaving the selection criteria to inference from the tool name.

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