List Lineage 2 private servers

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly indicates a read-only list operation, reveals the ordering ('ordered by VIP status and opening date'), and names the filtering dimensions. It leaves some details such as GVE exclusion and pagination to the schema, but the core behavior is transparent.

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 two concise sentences with no filler. It front-loads the core action and resource, then summarizes the optional filters in one efficient phrase. Every sentence earns its place.

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 simple optional-filter list tool with all six parameters fully documented in the schema, the description is nearly complete: it states the data source, ordering, and available filter categories. It does not describe the return shape, but there is no output schema and the absence is acceptable for this simple listing operation.

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 the baseline is 3. The description condenses the parameters into categories like 'upcoming openings, newly added entries or rate range', but adds no meaning beyond what the schema already provides for each parameter.

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 names a specific verb and resource: 'List Lineage 2 private servers tracked by L2 Calendar', and adds ordering and filter scope. It is clear, but it does not explicitly differentiate itself from the sibling search_servers or get_server 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?

The phrase 'List ... Optionally filter by ...' implies this tool is for listing and filtering servers, which gives reasonable usage context. However, it never states when to prefer this tool over search_servers or get_server, so alternative guidance is missing.

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