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

Annotations already declare the safe read profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), and the description adds substantial context about what is actually returned: run scheduling, monitor-specific settings, ignored findings, AI-authored fields, and the latest run. This is rich disclosure for a tool with no output schema, though it omits error/pagination behavior.

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?

It is a single sprawling sentence with nested parentheticals and a trailing ellipsis that signals unfinished enumeration. It is front-loaded with the key point ('One monitor in full') but the dense field listing hurts readability.

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 explaining return content, and it does so thoroughly, including the useful note that it reveals which sections update_check_settings accepts. Missing only error/edge-case behavior for a simple 1-parameter read.

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% and the single checkId parameter is fully documented in the schema (including its source: site_overview or add_checks). The description adds no further parameter meaning, 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?

It clearly designates a single-resource retrieval ('One monitor in full') and enumerates the categories of data returned, which distinguishes it from list_checks and from get_run (it only surfaces the 'latest run'). The retrieval verb is only implied rather than stated, but an agent can tell what the tool returns.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative such as list_checks. Usage is only implied by the enumerated contents, so an agent must infer that this is the detail view for a specific checkId.

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