monitor_certificate

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

With no annotations present, the description carries the full burden. It makes the operation appear read-only and informational by saying it 'checks' certificate details, which is useful. However, it does not disclose potential network behavior, failure modes for invalid certificates, timeout behavior, or response format.

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, front-loaded sentence that immediately states the action and the resource. Every word adds value, and it is appropriately sized for a simple monitoring tool.

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 basic hostname-and-port certificate check, the description plus schema provides enough to make an initial call. However, with no output schema and no annotations, it omits failure behavior, output format details, and guidance for choosing between this tool and security_ssl_analyze, leaving meaningful gaps.

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?

The schema documents hostname but not port, and the description does not compensate for the port gap. It does not mention that custom ports are supported, that 443 is the default, or explain the meaning of the port parameter. The description only indirectly adds meaning to hostname via the SSL/TLS certificate context.

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 uses the specific verb 'Check' and identifies a concrete resource: SSL/TLS certificate details, listing validity, expiration, issuer, and certificate chain. This makes the tool's function clear, but it does not differentiate it from the overlapping sibling security_ssl_analyze, so it stops short of a 5.

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?

The description provides no guidance about when to use monitor_certificate versus alternatives such as security_ssl_analyze or monitor_check_uptime. Usage context is only implied by the phrase 'certificate details'; no exclusions or alternative routing is provided.

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