web_ssl_check

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

No annotations provided, so description must carry full burden. 'Check' implies read-only access but fails to disclose if this makes live HTTPS connections, what specific details are retrieved (expiry, issuer, chain validity), or behavior on invalid/missing certificates.

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?

Single sentence, front-loaded with action verb, no waste. Appropriate length for tool simplicity.

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?

Adequate for basic 1-parameter tool, but gap remains: no output schema exists, yet description fails to hint at return structure (fields like expiry_date, issuer, valid boolean) or error conditions.

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 has 100% coverage with good example 'github.com'. Description adds no parameter-specific context, but baseline is 3 when schema carries full documentation load for simple single-parameter tool.

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?

States clear verb 'Check' and resource 'SSL certificate details' with scope 'for a domain'. Distinguishes from sibling web tools (dns_lookup, seo_check, fetch) by specifying SSL/certificate focus, though does not explicitly contrast with them.

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?

Provides no guidance on when to use versus alternatives like web_fetch (which retrieves page content) or web_dns_lookup (which checks DNS records). No mention of prerequisites or network requirements.

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