Find Endpoint

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about read-only behavior, permissions, side effects, or lookup scope. The single word 查询 implies a query but does not provide enough transparency for an agent to rely on it.

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, but this is under-specification rather than useful conciseness. For a three-parameter lookup tool with no annotations, it omits information an agent needs instead of being efficient.

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 an output schema exists and return values need not be described, the definition still lacks usage context, behavioral disclosure, and parameter semantics. Given the tool's place among many similar lookup siblings, the description is not complete enough to select or invoke it confidently.

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 0% across three parameters, and the description merely repeats the names 'IP' and 'Port' without adding format, range, or meaning. The optional protocol parameter is not mentioned at all, so the description does not compensate for the schema gap.

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 says only 'query specified IP + Port', which restates the required parameter names rather than explaining what an endpoint lookup returns or how it differs from siblings like find_port or is_port_used. It is a fragmentary purpose statement, not a useful distinction among the many find_* tools.

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 guidance is provided. The description does not mention alternatives, preconditions, or the context in which find_endpoint should be chosen over the numerous sibling lookup tools.

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