searchatlas_site_explorer

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

No annotations are provided, so the description carries full burden. It mentions 'audit and analysis' which implies read-only behavior, but doesn't disclose critical traits like whether it performs mutations, requires authentication, has rate limits, or what the output entails. For a tool with 4 parameters and no output schema, this lack of behavioral detail is a significant gap.

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 a single, efficient sentence that front-loads the core purpose without unnecessary words. It's appropriately sized for the tool's complexity, though it could be more structured by explicitly separating functions. Every part earns its place, making it concise.

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 complexity (4 parameters, no output schema, no annotations), the description is incomplete. It lacks details on behavior, output format, and how it integrates with siblings. For an analysis tool, more context on what 'audit and analysis' entails and the results is needed, making it inadequate for full agent understanding.

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 the schema already documents all parameters well. The description adds no additional meaning about parameters beyond the generic 'site audit and analysis' context. This meets the baseline of 3, as the schema handles the heavy lifting, but the description doesn't compensate or enhance parameter understanding.

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 states the tool performs 'site audit and analysis' with specific areas (crawl data, backlink profiles, competitive intelligence), which gives a general purpose. However, it doesn't specify a clear verb-action relationship or distinguish this from sibling tools like searchatlas_website_studio or searchatlas_authority_building that might have overlapping SEO functions, making it somewhat vague.

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 alternatives. It doesn't mention prerequisites, context, or exclusions, and with multiple SEO-related siblings, there's no indication of how this differs from tools like searchatlas_content or searchatlas_keywords, leaving the agent without usage direction.

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