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

With no annotations, the description carries the full behavioral burden. It helpfully discloses the specific checks and outputs, but it does not state whether the scan is read-only, whether authentication or rate limits apply, what errors may occur, or whether any side effects exist.

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 compact sentence with no filler and is appropriately sized for a preview scan. It is slightly back-loaded around return values rather than leading with the action, but remains efficient.

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 one-parameter preview tool with no output schema and no annotations, the description gives a solid list of returned checks. However, it omits usage context, safety/read-only behavior, error conditions, and rate or auth expectations that an agent would need for confident invocation.

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%, and the single domain parameter is already documented with an example in the schema. The description adds no extra syntax or format guidance beyond the schema baseline.

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 identifies a specific scan of a domain for AI/MCP readiness and enumerates concrete checks and return data, including AI Visibility Score, bot access, Shopify MCP endpoints, and citation preview. It is clear what the tool does, though it does not explicitly differentiate itself from the sibling tools.

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 explicit guidance on when to use this tool, when not to use it, or which sibling tool to choose instead. The 'Free Preview' framing in the title hints at a preview use case, but the description itself leaves usage to inference.

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