check_ssl_expiry

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the 'allowlisted' constraint, which hints at possible domain restrictions, but doesn't disclose what happens for non-allowlisted domains, whether the check is a live network lookup, or any side effects or rate limits. It's too sparse to be transparent.

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, focused sentence with no filler. It front-loads the verb and object, making it immediately parsable. The brevity is appropriate for a simple tool, though it sacrifices depth.

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?

The tool is simple with a single parameter and an output schema exists, so return values are presumably documented. However, the description omits critical usage context such as the allowlist enforcement behavior, possible error conditions, and when to choose this over the sibling tools. It's minimally complete but leaves clear 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?

Schema description coverage is 0%, so the description must compensate. The only hint is 'allowlisted domain' which suggests that the domain parameter must be pre-approved, but it doesn't explain the format, any constraints (e.g., FQDN vs URL), or what values are acceptable. The parameter name 'domain' is self-explanatory but the description adds little beyond that.

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 verb 'Return' and clearly specifies the resource ('certificate expiry details') and scope ('allowlisted domain'). It clearly distinguishes from sibling tools which target system health, containers, logs, and database status—none of which relate to SSL certificate details.

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 on when to use this tool versus alternatives. It doesn't mention any exclusions or prerequisites other than the implied 'allowlisted domain' constraint, which isn't elaborated as a usage condition. There are no explicit 'when to use' or 'instead of' statements.

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