check_ssl_health

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses detailed behavior: what it returns, that it performs live probes, that it flags env-var overrides pointing at missing paths, and that it provides a verdict and remediation steps. It appropriately declares itself 'Safe, read-only.' No contradiction with annotations.

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 front-loaded with the primary purpose and usage trigger, then moves through return contents and the probe toggle. It is somewhat dense and list-heavy, but every clause adds useful information. It is appropriately sized for a diagnostic tool with this much output.

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 has a rich output schema and full annotation coverage, so the description does not need to define every return field. It supplies the essential operational details: when to use it, what diagnostic categories it covers, what the verdict levels are, and how to switch to offline mode. This is complete enough for an agent to select and invoke it correctly.

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?

With 0% schema coverage, the description compensates by explaining the only parameter, probe, and its offline mode. It does not restate the default (true), but the schema already provides that. The semantic distinction between live probing and offline diagnostics is clearly conveyed.

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 a specific verb ('Diagnose') and resource ('Python SSL/TLS certificate configuration'), and clearly distinguishes the tool from siblings by tying it to specific failure modes (CERTIFICATE_VERIFY_FAILED, SSL errors, HTTPS failures). It also enumerates the concrete diagnostic outputs, making the purpose unambiguous.

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?

It explicitly states when to use the tool: whenever any tool reports CERTIFICATE_VERIFY_FAILED, SSL errors, or HTTPS failures, including named integrations. It also provides conditional usage guidance for the probe parameter ('Set probe=False for offline config-only diagnostics').

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