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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value beyond that by naming the fields returned (current status, last HTTP status, response time), but says nothing about pagination, result volume, or what happens for a site with no checks configured.

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 sentence that front-loads the resource and folds the disambiguating definition and the returned fields into the same clause. Nothing is wasted and nothing important is buried.

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 read-only, one-parameter list tool with no output schema, telling the agent which fields come back and what an endpoint check is makes the definition essentially self-sufficient. Only minor operational details (pagination, empty results) are absent.

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?

There is a single required 'site' parameter at 100% schema description coverage, so the schema already defines it as site id, domain or URL. The description reinforces the scoping ('one of your sites') but adds no format or resolution detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource and disambiguates the ambiguous term 'endpoint checks' with a parenthetical (GET/HEAD monitors for URLs like /api/health), plus scopes it to a single site. It clearly separates itself from list_sites and list_issues by resource, though it never names a sibling explicitly.

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 only implied: the tool is clearly the discovery step for per-site endpoint checks, but there is no statement of when to prefer it over get_site_status or list_issues, and no note that the site id typically comes from list_sites. Adequate context, no explicit exclusions or alternatives.

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