check_ssl_certificate

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

No annotations are provided. The description discloses that the tool returns HTTP status and server info, but lacks details on error handling, timeouts, or any side effects. It is somewhat transparent but could be more explicit about behavior when the domain is unreachable.

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 concise with two main sentences and a parameter section. It front-loads the core function and usage guidance without any unnecessary words.

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 tool's simplicity (one parameter, no nested objects) and the existence of an output schema, the description covers the purpose, usage, and return type adequately. It does not explain the output structure, but that is compensated by the output schema.

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%. The description includes a 'Parameters' section that repeats the domain parameter with an example, adding minimal context beyond the schema. For a single parameter, the provided format hint is helpful but not extensive.

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 tool checks if a domain has a valid SSL/TLS certificate and is reachable, using specific verbs and resources. It distinguishes from sibling tools like analyze_url or http_client by focusing on SSL validity and serving over HTTPS verification.

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 advises using this tool to verify HTTPS before making requests, providing clear context. It does not mention when not to use or alternatives, but the guidance is sufficient given the tool's specific purpose.

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