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

The annotations declare readOnlyHint: true, indicating a safe read operation, but the description fails to add behavioral context. It doesn't disclose that the tool performs crawling, respects depth limits, or requires JavaScript rendering for some sites. No mention of performance characteristics, rate limits, or edge cases beyond what the schema's parameter descriptions already provide.

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 single-sentence description is concise but under-specifies the tool's behavior. It's not powerful or informative enough to earn credit for conciseness; rather, it reads as an under-developed placeholder. A good description would front-load the tool's purpose in a way that adds value, but this wastes the opportunity.

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 tool with 9 parameters, a required URL, and complex behaviors like crawl depth, subdomain handling, and JavaScript rendering, a one-sentence description is grossly inadequate. Even though an output schema exists, the description fails to convey the tool's inputs' intent or the meaning of its output. The behavioral nuances (e.g., proxy usage, OR-matching for keywords) are left entirely to the schema, making this incomplete.

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 description coverage is 100%, so all 9 parameters are documented in the input schema itself. The description adds no parameter semantics; it merely repeats the tool name. Per rubric, with high schema coverage, the baseline is 3, which is appropriate here since the description doesn't need to compensate but also doesn't add value.

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 'Tool useful for mapping website's URLs' uses the vague verb 'mapping' and a possessive phrasing that doesn't define the action clearly. While it names the resource (website URLs), it fails to articulate the core function of discovering or crawling links, leaving the tool's true purpose ambiguous. Sibling tools like 'ai_crawler' and 'ai_scraper' further blur the line, making this description insufficiently specific.

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 provides no guidance on when to use this tool versus any of the nine sibling tools. There is no mention of when ai_map is preferred over ai_crawler or ai_browser_agent, nor any exclusions or prerequisites. Users are left to guess which tool fits their use case.

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