whats_changedFreshness and change state: when the index was built, when each operator source was last fetched, which changed, which are failing, and the dated changelog. The cron check before regenerating a config from this data. Example: since='2026-08-01'.
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | ISO-8601 date or timestamp; omit for the current state. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only and idempotent behavior. The description adds context that it is safe for cron checks (implying repeated use without side effects) and describes the nature of the output (failures, changelog), which goes beyond the annotations.
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 concise (three sentences), front-loads the primary purpose, and includes a practical example. It avoids unnecessary detail and is well-structured.
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 gives a good sense of the output (freshness, change state, failures, dated changelog) and the usage scenario. It does not explicitly mention the domain (crawlers), but sibling context implies it; still, it is reasonably complete for an agent to understand the tool's role.
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% for the single optional 'since' parameter, with a clear description. The tool's description adds an example but does not further elaborate on parameter semantics beyond the schema, so a 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 clearly states the tool's purpose: reporting freshness and change state (index build time, last fetch, failures, changelog). It also provides an example and distinguishes it from sibling tools about crawlers and user agents by focusing on change detection.
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 mentions 'The cron check before regenerating a config from this data,' indicating when it should be used. It does not discuss alternatives or when not to use it, but the usage context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct action: classifying user-agent strings, verifying IP addresses, listing, looking up, generating robots.txt, and checking data freshness. The explicit cross-reference between classify_user_agent and is_verified_crawler_ip clarifies rather than blurs their boundaries.
Almost all tool names follow a predictable snake_case verb_noun pattern such as classify_user_agent, list_crawlers, and lookup_crawler. whats_changed deviates slightly from the verb_noun style but remains consistent in lowercase snake_case, so the naming is mostly coherent.
Six tools is a well-scoped set for a crawler index service. Each tool covers a distinct need without overlapping or unnecessary additions.
The tool surface covers the full workflow for understanding and managing crawler data: discovery, identification via UA or IP, detail lookup, robots.txt generation, and freshness monitoring. No obvious dead ends or missing operations for the stated purpose.