impreza_domain_check

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

The description explicitly states 'Read-only', which is critical given no annotations. It conveys that the tool performs a safe query without side effects. However, it could mention that it doesn't modify any resources or affect domain registration.

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 concise with two sentences, front-loading the purpose and then providing usage details. Every sentence serves a purpose without redundancy.

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 covers the basic function and input format, but it lacks information about the output or return values. For a checking tool, an agent would benefit from knowing what the response contains (e.g., boolean availability, price). No output schema is provided, so the description should compensate.

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 input schema already describes the 'domain' parameter with examples, achieving 100% coverage. The description adds only minor clarification about comma-separated domains. Since schema coverage is high, the description adds limited value beyond the schema.

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 clearly states the tool checks domain availability and price, using the verb 'Check' and specifying the resource. It distinguishes from siblings like 'impreza_domain_details' by focusing on pre-registration checks.

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 phrase 'before registering' provides clear context for when to use this tool. While it doesn't explicitly mention when not to use it or list alternatives, the context is sufficient for an agent to choose it over other domain tools.

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