List TCP fingerprint profiles

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real conceptual context about what a TCP/IP fingerprint preset is and why you would want one. It doesn't cover return volume or how include_details changes the payload, but the added domain meaning is substantive with no contradiction.

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?

Two sentences, front-loaded with the verb and resource, with the alternative mentioned last. No filler; the conceptual explanation earns its place by disambiguating a jargon-heavy term.

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 read-only list tool with fully documented parameters and no output schema, the description supplies enough to call it correctly and understand the payload's significance. Return-shape and pagination details are the only gaps, and they are minor here.

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 both parameters (category, include_details) are already documented, giving a baseline of 3. The description's parenthetical OS list loosely maps to the category enum but adds no syntax or filtering detail beyond the schema.

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 (Lists) and resource (TCP/IP fingerprint presets), defines what those presets are (OS signatures for proxied traffic), and names the sibling set_tcp_fingerprint as the apply-action counterpart. An agent can distinguish it from get_tcp_fingerprint and set_tcp_fingerprint without opening any schema.

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 use case is clear (pick a preset consistent with the client device) and it explicitly points to set_tcp_fingerprint as the tool that applies one. It stops short of stating when-not to use it or naming all nearby siblings, so it sits just below the explicit when/alternatives bar.

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