Check SSL Certificate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the tool's behavior by listing what it inspects (issuer, validity dates, etc.) and what it flags (expired, soon-to-expire, self-signed), giving clear operational context. However, it doesn't mention potential limitations like rate limits, authentication needs, or error handling for invalid domains.

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 efficiently structured in two sentences: the first explains what the tool does with specific details, and the second provides usage context. Every phrase adds value without redundancy, making it easy to parse and understand quickly.

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 single-parameter tool with no annotations and no output schema, the description provides strong context about what the tool inspects and flags, plus clear usage scenarios. It adequately compensates for the lack of structured output information by describing the certificate attributes examined. A minor deduction because it doesn't specify the exact return format or potential error cases.

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% with the single 'domain' parameter fully documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., format examples or edge cases), so it meets the baseline of 3 where the schema does the heavy lifting.

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 clearly states the specific action ('Inspect a domain's TLS/SSL certificate') and resource ('domain'), listing detailed attributes like issuer, validity dates, SANs, etc. It distinguishes from sibling tools by focusing exclusively on SSL certificate inspection rather than accessibility, SEO, broken links, or other web analysis functions.

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 explicitly states when to use this tool: 'Use for devops monitoring and pre-launch verification.' It also provides implicit context by listing what it flags (expired, soon-to-expire, self-signed certs), helping differentiate from other tools like 'check_status' or 'dns_lookup' that might handle different aspects of domain checking.

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