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 states the outcome ('which SSL/TLS protocols the host accepts') but does not explain whether this is a network scan, an external lookup, what happens on failure, or any safety or latency implications.

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 very short and front-loaded, with no meaningful filler. The leading label 'TLS Versions:' is somewhat redundant with the tool name, but the overall definition is compact and easy to parse.

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?

Although the tool is simple and an output schema exists, the description still fails to define the input meaning for q or the expected host format. An agent would have to guess what value to pass, especially given the optional parameter with an empty default. The description is not self-sufficient.

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 the description must compensate for the undocumented 'q' parameter. The word 'host' hints that q is the target host, but the description does not explicitly define q, its expected format, or what an empty default means. This is only partial compensation.

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 identifies the tool's function: determining which SSL/TLS protocol versions a host accepts. It is specific about the resource (TLS versions) and the host's behavior, though it lacks an explicit verb and does not differentiate from sibling tools like 'tls' or 'tlsa'.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The description only implies that the tool checks supported TLS versions, but it never says when an agent should select tlsscan over the many related sibling tools.

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