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

With no annotations, the description carries the burden of explaining behavior. It conveys that the tool performs checks and returns a summary, suggesting a read-only operation. It does not disclose auth requirements, rate limits, or what 'open incidents' means, but the stated output fields provide reasonable transparency for a simple health 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?

The description is a single front-loaded sentence with a compact, useful list of returned information. Every word adds value and there is no filler 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?

For a simple one-parameter read tool, the description covers the core purpose and main output categories. It is not fully complete because it lacks parameter format guidance and does not clarify how this tool relates to verify_site or other health-adjacent tools, but the overall complexity is low.

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 schema only defines a required string named 'site' with no description, and schema description coverage is 0%. The description says the summary is 'for a site,' but does not specify whether the value should be a domain, URL, or site ID, leaving an important ambiguity.

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 provides an uptime/health summary for a site, listing specific contents like status, response time, TLS/domain checks, and open incidents. This distinguishes it from reporting tools like get_stats or get_realtime, though it does not explicitly name any sibling alternative.

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?

Usage is implied: when you need a site's uptime/health summary, this is the tool. However, there is no explicit guidance about when to choose this over related tools such as verify_site or get_breakdown, and no exclusionary conditions are mentioned.

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