inspect_ssl_cert_chain

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

With no annotations, the description carries the burden, and it does disclose non-obvious behavior: it does not crash on self-signed or expired certificates, and it reveals a payment requirement of 0.01 USDC on Base L2. It does not detail output or network behavior, but the most important behavioral guarantees are present.

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 tight sentence that front-loads the purpose, states the key robustness guarantee, and appends the cost parenthetically. Every element earns its place with no filler.

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's purpose and cost are clear, but it omits essential invocation details: what the payload should contain (domain, URL, PEM data, etc.) and what the audit result looks like. Since there is no output schema and the parameter schema is generic, the agent is left guessing about input formatting and return shape.

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 100%, so the baseline is 3 even without parameter detail in the description. However, the description adds no extra meaning about how the payload should encode the target host, port, certificate, or chain, leaving the actual invocation format ambiguous.

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 states a specific action ('Audits') and the exact resources/metrics: SSL/TLS certificate chains, SAN domains, and expiration dates. It also distinguishes itself by promising robustness on self-signed or expired certificates, which clearly separates it from generic network or validation tools.

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 clearly implies when to use the tool: when an agent needs to audit certificate chains, SANs, or expiry dates, especially with invalid certificates present. It does not explicitly name alternatives or exclusions, but no sibling tool overlaps directly with SSL/TLS chain auditing, so the context is sufficient.

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