Tls Check

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the certificate aspects covered (expiry, chain, issuer) but does not disclose whether the tool performs a live network connection, whether it requires a host/port parameter, what happens on certificate errors, or what the output structure looks like. The description is a terse label rather than a behavioral contract.

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 extremely short, which is concise, but it is under-specified rather than efficiently informative. It front-loads the key aspects (expiry, chain, issuer) but omits essential usage and parameter context. It earns a middle score because it is not verbose, yet it does not fully earn its place as a standalone definition.

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 has no annotations, no parameter documentation, and a generic params object, the description is far from complete. The output schema exists but the description does not explain how to invoke the tool or what inputs are required. For a network diagnostic tool among many siblings, an agent needs more context to select and call 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?

The input schema has a single 'params' object with additionalProperties true and no described properties, so schema description coverage is 0%. The description does not compensate by explaining what parameters are needed (e.g., host, port, domain). An agent has no idea what to pass in the params object, making this a significant gap.

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 'TLS сертификат: expiry, chain, issuer' identifies the resource (TLS certificate) and the aspects it covers (expiry, chain, issuer), so an agent can infer the tool checks TLS certificate details. However, it lacks a specific verb like 'check' or 'get', and it does not distinguish this from other network diagnostic tools such as http_check, tcp_connect, or dns_resolve. The title 'Tls Check' adds little beyond the name.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list includes many network and diagnostic tools, but the description does not mention any conditions, prerequisites, or exclusions. An agent would have to infer that this is for TLS certificate inspection, with no help on when to prefer it over http_check or tcp_connect.

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