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

Annotations already declare readOnly/destructive=false, but the description goes well beyond them by enumerating the returned payload: ordered components with the ids the component tools consume, public URL, subscriber count, and custom-domain DNS/verification/certificate state. With no output schema present, this disclosure is exactly the missing behavioral context.

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?

Two dense sentences: trigger conditions first, return contents second, exclusion last. Every clause carries information and nothing is repeated from the schema or annotations.

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?

A single-parameter read tool with no output schema, so the description must carry return-value burden — and it does, covering components, URL, subscribers, and domain health. Nothing an agent needs to call this correctly is missing.

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% and the single parameter is documented as 'The page's id or name', so the baseline is 3. The description does not add resolution semantics the schema lacks, such as what happens with an ambiguous or unknown name, or whether lookup is case-sensitive.

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?

Specific verb and resource ('what one of their status pages shows, which sites and checks are on it') with a clear scope boundary against list_status_pages and list_incidents. An agent can distinguish this from every sibling without opening the schema.

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?

Names three concrete triggering user intents (what the page shows, which sites/checks are on it, why the custom domain is broken) and an explicit exclusion with the alternative tool ('Not for incidents posted on it: use list_incidents'). Both when-to-use and when-not-to-use are stated.

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