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 real value by disclosing the payload contents — change since previous scan, severity breakdown, 24h and 7d uptime, and last-scan deltas. It does not cover behavior for an unknown/unmonitored site or whether the data is cached versus freshly scanned.

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 most important returned value (latest score with change) before the secondary contents. Nothing is redundant with the title or schema, and no filler text is present.

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?

With no output schema, the description correctly carries the return-value burden by enumerating the fields the agent will receive. It is nearly complete for a one-parameter read tool, though it omits error behavior for an invalid/unmonitored site and the units/scale of the score.

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 'site' parameter is already documented as 'Site id, domain or URL'. The phrase 'one of your monitored sites' adds the constraint that the site must already be registered, but no format examples or resolution rules are added beyond the schema. 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?

The description enumerates exactly what the tool surfaces for a single monitored site (score + delta, issues by severity, top issues, uptime, recent changes), which is more specific than the title's 'Get site status'. It implies single-site scope, distinguishing it from aggregate siblings like list_sites or list_issues, but never names those siblings directly.

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: 'for one of your monitored sites' signals a single-site snapshot use case. There is no explicit statement of when to reach for this versus list_issues, explain_issue, get_report, or recheck_site, and no prerequisites (e.g., that the site must already be added via add_site).

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