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

With no annotations provided, the description carries the full burden. It explicitly states this is a read operation and enumerates the returned data (page name, overall status, per-component status/uptime, active incidents/maintenance). It also discloses the one-of constraint. It does not mention error handling or non-mutating guarantees explicitly, but 'Read' implies safety.

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 three sentences with zero fluff. It front-loads the purpose, then returns, then lookup mode and constraint. Every sentence contributes essential information.

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?

No output schema exists, so the description adequately compensates by listing return values. It covers input modes and the one-of rule. The only gap is not specifying behavior when both slug and domain are provided, but for a read-only lookup tool this is a minor omission.

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%, so the baseline is 3. The description adds value beyond the schema by introducing mutual exclusivity ('Provide exactly one of slug or domain') and by illustrating how each parameter is used via hosted.nslookup.io/slug and custom domain examples, which the schema descriptions do not fully convey.

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 uses the specific verb 'Read' and clearly identifies the resource as a 'public status page hosted on nslookup.io status pages.' This distinguishes it from sibling tools like uptime_check or my_incidents, which target different resources or user-specific data.

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 clear lookup context: by slug or custom domain, with the explicit instruction to provide exactly one of them. However, it does not name alternative tools or state when not to use this tool, so it stops short of explicit exclusions.

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