Create SSL certificate monitor

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

Annotations already indicate this is not read-only (readOnlyHint=false) and not destructive, so the description need not repeat those. It adds value by disclosing that the monitor has two independent states (reachability and expiry) and that the check can read 'up' while the certificate is expiring. While this is useful, it does not fully detail all behavioral aspects (e.g., alerting), but given annotations cover the safety profile, this is well above baseline.

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?

The description is a single paragraph of two sentences, directly conveying the purpose, scope, and a key behavioral nuance. Every sentence adds value, with no filler or redundancy.

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?

Given the annotations (readOnlyHint=false, destructiveHint=false) and the rich output schema (not shown but indicated as present), the description covers the essential conceptual nuance (certificate vs reachability) that is not evident from the schema. It is complete for the tool's scope and context, as the output schema handles return value details.

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%, so the description does not need to explain parameters individually. It does not add extra meaning beyond the schema, but the schema already provides clear descriptions for url, name, and isActive. Therefore, a score of 3 is appropriate as the description does not repeat parameter details.

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 states precisely that the tool creates a monitor that watches a TLS certificate's validity, issuer, and days to expiry. It distinguishes its scope from site reachability and explicitly names the sibling tool create_http_monitor for that complementary purpose.

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?

It gives clear guidance: use this for certificate-focused monitoring reliable, and pair it with create_http_monitor when both certificate and site reachability are needed. This explicitly states when to use and when not to use, directly addressing the sibling comparison.

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