check_domain

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

No annotations provided, so description bears full burden. It reveals the data source (Common Crawl) and indexed size, which adds transparency. However, it does not mention rate limits, caching behavior, or data freshness—information that would be helpful for a read 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?

Three sentences: action, output, usage guidance. No wasted words, front-loaded with purpose. Efficient and clear.

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?

Single required parameter with full schema coverage; output explained in description. No output schema needed as description lists returned fields. No omitted critical details for a simple authority check tool.

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 coverage is 100% with clear description of domain parameter (stripping protocol/www). Description adds example values and clarifies cleanup behavior, exceeding what schema provides.

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?

Clearly states the tool checks backlink authority for a domain, listing specific metrics (DR, centrality, PageRank, referring domains). Distinguishes from siblings such as get_referring_domains (focused on backlinks) and get_domain_info (likely different info).

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?

Explicitly advises usage when user asks about backlink profile, authority, or domain comparison. Does not provide when-not-to-use or alternatives, but the context is clear enough given the sibling list.

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