decrypt_tls_traffic

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

Annotations already mark readOnlyHint=true and idempotentHint=true. The description adds behavioral context: it requires an NSS-format key log file, and optionally writes a decrypted pcapng file. No contradictions.

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?

Very concise: 6 sentences covering purpose, requirement, and parameters. Front-loaded with the core function. Every sentence adds value.

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 3 simple parameters and no output schema, the description fully covers inputs, prerequisites, and optional output. No gaps.

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 0%, so description carries full burden. It explains each parameter: filepath (PCAP/PCAPNG), keylog_file (TLS key log), output_file (optional decrypted output). Provides meaning beyond bare types.

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 clearly states the tool decrypts TLS/HTTPS traffic using an SSLKEYLOGFILE, with specific verb 'decrypt' and resource 'TLS traffic'. It distinguishes from siblings like analyze_http_traffic which handle unencrypted packets.

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 explains the requirement of a TLS key log file captured alongside traffic and offers two ways to provide it (env var or explicit parameter). It lacks explicit when-not-to-use or alternatives, but the context is sufficient for agents.

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