Force a full re-crawl of a site to pick up new or changed content. If the site has never been indexed, AgentReady performs the initial indexing automatically. Use when ask_site returns outdated information or when you know the site has recently been updated. Takes ~60 seconds. After completion, ask_site returns fresh content.
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes | Domain of the site to refresh (e.g. "docs.example.com"). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears the full burden and does well: it reveals the operation takes '~60 seconds,' performs automatic initial indexing for never-indexed sites, and ensures 'ask_site returns fresh content' after completion. This gives the agent a clear expectation of side effects and outcomes.
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, front-loaded with the core action, and every sentence adds value: the action, the auto-indexing behavior, the use case, and the duration/outcome. No redundant or vague language.
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?
Given the lack of annotations and output schema, the description covers the important context: what the tool does, when to use it, how long it takes, and what the user can expect afterward. It could go deeper on potential failure modes or side effects, but it is reasonably complete for a simple single-parameter 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 sole parameter (domain) has 100% schema coverage with a clear example. The description itself does not add extra meaning to the parameter beyond what the schema already provides, so the baseline 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 clearly states the tool's primary action: 'Force a full re-crawl of a site to pick up new or changed content.' This is a specific verb (re-crawl) with a clear resource (a site). It also distinguishes itself from siblings by contrasting with ask_site, which queries existing content.
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?
Provides explicit when-to-use guidance: 'Use when ask_site returns outdated information or when you know the site has recently been updated.' This clearly frames the tool's purpose relative to its sibling. It does not explicitly mention when not to use it, but the context is sufficient.
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 operation: querying, listing, managing, rating, planning, refreshing, and submitting sites. Even similar operations like refresh_site and submit_site are clearly differentiated by whether the site is already indexed.
All tool names follow a consistent verb_noun pattern (ask_site, list_sites, submit_site, etc.), making the API predictable and easy to navigate.
7 tools is well within the ideal range for a focused website indexing service. Each tool earns its place and together cover the core workflow of indexing, querying, refreshing, and managing sites.
The lifecycle for sites is mostly covered: submit (create), refresh (update), list/ask (read), but there is no delete/remove site operation. Minor gap that agents can work around by ignoring obsolete sites, but a delete tool would make it fully complete.