cc_crawls

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

No annotations are provided, so the description must carry the behavioral transparency burden. It does not disclose whether the request is read-only, whether results are cached, or what the 'refresh' parameter does. This is a significant gap for a tool with an optional refresh parameter.

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 short sentences, front-loaded with the main purpose. No wasted words, and it efficiently conveys the key point about ordering and usage.

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?

For a simple list tool with an output schema, the description is adequate but has clear gaps: it omits the refresh parameter's behavior and any note about read-only semantics. It lacks details that would help an agent fully anticipate the tool's behavior, even though the output schema covers return values.

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 schema has one boolean parameter 'refresh' with 0% description coverage. The description does not mention this parameter at all, failing to explain its purpose or effect. The parameter name hints at refreshing but is not explicit, so the description adds no value beyond the schema.

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 lists available Common Crawl crawls, with the newest last. This distinguishes it from sibling tools that focus on specific aspects like presence or dynamics.

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?

It explicitly says this is useful to get the current crawl name before making other requests, providing clear context for when to use it. It doesn't mention alternatives or exclusions, but the primary use case is well stated.

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