wais_discover

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

With no annotations provided, the description fully informs the agent that it fetches /.well-known/agents.json and returns a summary including site URLs, actions, parameters, and registration info. It discloses that the agents.json is the source of truth, though it does not cover potential failure cases or rate limits.

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 well-structured: it starts with the purpose and usage, then briefly describes the fetch action and returned fields, and ends with the parameter description. Every sentence adds value 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?

Given the tool's simplicity with one parameter and an output schema, the description is fully complete. It explains what the tool does, what it returns, and how to use the results with sibling tools, leaving no gaps.

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 has 0% description coverage, so the description compensates by explaining the site_url parameter: 'The site's URL (e.g. 'https://serphub.deeger.io').' This adds essential meaning beyond the schema alone.

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: 'Discover what a WAIS-compatible site offers. Call this first for any site.' It uses a specific verb (discover) and resource (WAIS site capabilities), and distinguishes itself from sibling tools like wais_execute by directing the agent to use this tool first.

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 'Call this first for any site' and explains that the agents.json is the source of truth for action IDs used in wais_execute. While it does not mention when not to use it, the context implies this is the initial step, providing clear usage guidance.

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