check_tls_posture

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only describes the high-level inventory/highlighting function and does not reveal whether the tool is read-only, whether it requires a file path to a capture, how it handles malformed input, or what side effects or limitations exist.

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 concise sentence with no wasted words, and the key function is front-loaded. It loses a point because it is so sparse that it omits necessary context about the required parameter and usage boundaries.

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?

Even though an output schema exists, the description is incomplete for practical invocation: the required 'path' parameter is unexplained, there is no guidance on input type, and there is no differentiation from related TLS/security-analysis siblings. An agent would need to inspect external documentation or guess to call this 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?

Schema description coverage is 0%, and the description does not mention the required 'path' parameter at all. The agent is left to guess whether 'path' is a file path, directory, URL, or something else, and no guidance is given about acceptable formats or meaning.

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 verb ('Inventory'), a specific resource ('TLS handshake versions and SNI'), and a clear goal ('highlighting legacy protocols'). However, it does not explicitly distinguish this tool from related siblings such as analyze_handshake_failures or show_protocol_hierarchy, so it stops short of full sibling differentiation.

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?

The description gives no guidance on when to use this tool versus alternatives like inspect_http_requests, inspect_dns_queries, or analyze_handshake_failures. It implies a TLS security posture use case, but it never states conditions, exclusions, or relevant scenarios.

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