List all websites currently indexed in AgentReady. Use this to check if a domain is already available before submitting it — indexed sites return instant cited answers via ask_site. The index covers developer tools, APIs, cloud platforms, frameworks, databases, and more, and grows as new sites are submitted.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the index 'grows as new sites are submitted', adding behavioral context. However, it does not mention output format, pagination, or other response traits. With no annotations, the description carries the full burden, and the coverage is minimal for a simple list tool.
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 and front-loaded: the first sentence states the core action, and the second adds usage context and dynamic behavior. Every sentence earns its place without redundancy.
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 no-parameter tool, the description covers purpose, usage, and dynamic growth. However, it does not specify what a listed 'website' entry looks like (e.g., URL, name), and there is no output schema to fill that gap. This is a minor but notable omission.
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 tool has zero parameters, so schema description coverage is trivially 100%. Per the guidelines, a zero-parameter tool gets a baseline of 4, and the description does not need to compensate.
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 'List all websites currently indexed in AgentReady' with a specific verb, resource, and scope. It also distinguishes from siblings by referencing the submission workflow and ask_site, making its role clear.
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 explicitly says 'Use this to check if a domain is already available before submitting it', providing a clear when-to-use. It references ask_site as a downstream tool for cited answers, but does not explicitly enumerate alternatives or exclusions.
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.