ssl_inspect

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

Annotations set destructiveHint: true, implying the tool may modify state, but the description calls it 'Inspect' (read-only). No clarification is provided about side effects (e.g., network connections that could trigger alarms), rate limits, or the impact of the destructive hint. This inconsistency reduces transparency.

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 a single sentence, front-loaded with the action and resource. Every word is necessary and adds value. No redundant statements or fluff.

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 tool with two simple parameters and no output schema, the description adequately covers what it does and what it returns. However, it does not mention error conditions (e.g., unreachable host) or the fact that port must be numeric, but these are minor given the schema already specifies type number.

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?

Both parameters have schema descriptions (100% coverage). The description adds contextual meaning by explaining what the tool does with the inputs (inspects certificate chain) and what it returns, which complements the schema. It does not repeat schema details but enhances understanding.

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 the verb 'Inspect' and identifies the resource as 'full TLS certificate chain of a host'. It lists specific return values (expiry countdown, issuer chain, SANs, key size, weak-config warnings), making the tool's purpose concrete and distinct from sibling network tools like banner_grab or port_scan.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., banner_grab also deals with TLS). The description does not mention prerequisites, typical use cases, or scenarios where other sibling tools would be more appropriate.

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