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

Annotations declare readOnlyHint=true and idempotentHint=false, so the safety profile is partly carried structurally. However, the description never discloses that the Add/Remove variants create and delete persistent monitors, that monitors can fire webhooks and run on interval_s schedules, or that interval_s/webhook/min_cert_days only matter in the scheduled case. 'Right now' implies Check is a one-shot read, but the presence of write actions under a readOnlyHint is a material disclosure gap.

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 front-loaded sentence with no filler, which is good discipline. The brevity is under-specification rather than efficiency, though: the sentence earns its place but far more was needed given the schema complexity.

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 tool with a deeply nested discriminated-union schema, zero parameter descriptions, and no output schema, one sentence is not enough. Missing are the action variants, what a Check returns versus a List, and how often a scheduled monitor fires.

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 0%, so the description must carry the load and it explains almost nothing. It hints at the three target types (Http/Tcp/Tls) but says nothing about the action discriminator, and nothing about keyword, expect_status, min_cert_days, interval_s, name, or webhook semantics.

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 verb+resource is specific for one code path: it says it checks a website, port, or TLS certificate, and 'right now' signals immediate one-shot evaluation. But the schema exposes four actions (Add, Remove, List, Check) and the description covers only Check, so an agent reading it would not learn that this tool also registers and deletes persistent uptime monitors.

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?

No guidance on when to use this versus anything else, and no explanation of how the four mutually exclusive action variants relate (e.g. when to Add versus one-shot Check). The reader must reverse-engineer intent from a deeply nested oneOf schema.

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