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

Description aligns with annotations (readOnlyHint, openWorldHint, destructiveHint=false) and adds practical context that the check is free and verifies reachability/eligibility. No side effects are implied or hidden.

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?

A single, focused sentence conveys purpose, cost, timing, and criteria without unnecessary detail or repetition.

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?

The description sufficiently conveys the tool's core function and eligibility criteria. Since no output schema is provided, a brief statement of what the check returns could improve completeness, but the current wording implies a yes/no eligibility result.

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 only parameter, url, is fully covered by the schema with type and format. The description adds that the website must be public, but does not elaborate on expected URL variants or constraints; schema coverage is high, so baseline is appropriate.

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's verb ('Check'), resource ('website'), and specific purpose ('reachable and eligible before purchasing an audit'). It is readily distinguished from siblings like discover_products and get_purchase_instructions.

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 frames when to use the tool ('before purchasing an audit') and notes it is free. It does not name alternative tools for other scenarios, but the timing and eligibility context provide adequate guidance.

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