ssl_inspector__inspect_ssl_bulk

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

With no annotations, the description carries the full behavioral burden, yet it discloses only one trait: parallel execution. It says nothing about network/auth requirements, timeout or partial-failure behavior (what happens when one domain fails), rate limiting, or what the per-domain output looks like.

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?

A single tight sentence with the key scoping fact ('multiple domains in parallel') front-loaded and zero waste. It is efficient, though the brevity contributes to the gaps in behavioral detail rather than being purely a virtue.

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 network-touching tool with three parameters, no annotations, and no output schema, the description leaves too much unexplained: what 'TLS configuration' covers, whether results are per-domain error objects or aggregated, and how failures are reported. The schema covers inputs, but the tool's behavior and return shape are undocumented.

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 coverage is 100%, so hosts, port, and probes are already fully documented, including the probe cost (8 extra handshakes per domain). The description adds nothing about parameter semantics beyond restating 'multiple domains', so the baseline 3 applies.

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?

States a specific verb and resource (inspect TLS configuration) with an explicit scope qualifier (multiple domains, in parallel), which implicitly separates it from the single-domain sibling inspect_ssl. It stops short of naming the sibling outright, but an agent can still tell the bulk variant from the single-target one.

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?

Usage is only implied: 'multiple domains' signals this is for batch work while inspect_ssl handles one host. There is no explicit when-to-use/when-not, no guidance on choosing between this and check_cert_expiry or get_cert_info, and no advice on list size or batching.

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