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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered structurally. The description adds the underlying API route (GET /results/summary/{id}), but says nothing about retention window, rate limits, or whether the summary is computed live or cached. Adequate, not rich.

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 compact sentences, front-loaded with the output content and followed by the endpoint mapping. No filler, no restatement of the title.

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 carries the burden of describing returns, and it does list the aggregated metrics. However, for an hourly summary tool there is no date-range parameter and the description never states the default time window or number of hours returned, which an agent needs in order to interpret the result correctly.

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 description coverage is 100%: check_id's format and provenance (from nodeping_list_checks) and the MSP-only semantics of customer_id are fully documented in the schema. The description adds no parameter detail, so the baseline of 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+resource ('Hourly summary of a check's results') plus the exact aggregation granularity (per UTC hour) and the returned metrics (count, min, max, average run time), which distinguishes it from siblings like get_check_results and get_check_uptime. It does not, however, explicitly name which sibling to prefer for which need.

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: an agent can infer this is for aggregated run-time statistics rather than raw results. There is no explicit when-to-use guidance, no mention of when to prefer get_check_results / get_check_uptime instead, and no stated prerequisites or check_id sourcing (that only appears in the schema).

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