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

With no annotations, the description carries the full behavioral burden. It does disclose the protocol (TCP), the return (first banner), and a 500-char cap, but says nothing about connection timeouts, behavior when no banner is returned, or the security implications of connecting to arbitrary hosts.

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?

One front-loaded sentence that earns its place, followed by a short access/pricing note. No padding or repetition, though the emoji-laden billing line is slightly out of register for a technical tool description.

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-facing tool with no annotations, no output schema, and one undocumented parameter, the description leaves meaningful gaps: timeout/error behavior, whether the connection is authenticated, and what 'input' is for. It is minimally viable but not complete.

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. It explains 'host' and 'port' well enough semantically, but the third parameter 'input' is never mentioned and there is no format guidance (port is typed as string, unexplained). Partial compensation, not full.

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 chain: connects over TCP to a host/port and returns the first banner, capped at 500 chars. An agent knows exactly what this does, and there is no competing banner-grab sibling to disambiguate against.

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?

No when-to-use, when-not-to-use, or alternative guidance. The only routing-relevant line is a pricing/access note ('5 free trial calls per signed wallet'), which tells the agent about billing, not about when this tool is the right choice.

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