list_servers

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

No annotations provided, and the description only covers basic pagination. It fails to disclose ordering, rate limits, or behavior on empty results. For a listing tool, more transparency is needed.

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 short and front-loaded with the main purpose. The parameter listing is clear, though it could drop the 'Args:' prefix for brevity.

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?

Given the existence of an output schema (not shown), the description covers the essential purpose and pagination parameters. However, lacking details on filtering or ordering, it is slightly incomplete for a list 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?

The description adds default values and maximum for page_size beyond the input schema, which has no descriptions. With 0% schema coverage, this compensation is helpful but could include more detail on parameter usage.

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 explicitly states 'List all VPS servers in your account.' with a clear verb and resource. It distinguishes from sibling tools like get_server (single server) and create_server (creation).

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 guidance on when to use this tool versus siblings such as get_server for a specific server or search_domains. No exclusions or context provided.

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