port_check

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It does mention the cost ($0.001 USDC via x402), which is useful, but it omits any side effects, permissions, required network access, or what the tool actually does besides 'check'. This leaves the agent guessing about the operation's impact.

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, but the first phrase 'port check' is redundant with the tool name, detracting from value. The cost information is the only substantive detail. It is concise but under-specified, not a model of efficient clarity.

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?

The tool has no output schema and the description does not explain return values, expected input structure, or how it differs from similar network tools. The cost mention is the only completion, leaving the tool largely undefined for an agent to invoke 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?

The input schema only has a generic 'params' object with a self-referential description ('Tool parameters as JSON object'), providing no actual parameter names or types. The description adds no parameter information, so the agent cannot construct a valid request (e.g., knowing to pass a host and port).

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 'port check — Security & Network tool' essentially restates the tool name with a broad category. It does not specify what aspect of a port is checked (e.g., open/closed, service detection, firewall rules), making it a tautology rather than a clear functional explanation.

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 provides no guidance on when to use this tool versus the many sibling network tools (ping, traceroute, dns_lookup). The only context is the 'Security & Network tool' category, which is too vague to inform selection. No alternatives or exclusions are mentioned.

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