List webhostings

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds real value by listing the returned data (usage/limits, home directory, MySQL host) and the cross-tool key relationship. It does not discuss pagination behavior, though the schema's page/limit parameters imply 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?

Two tight sentences: purpose and payload first, then the practically important key mapping. No filler, nothing buried.

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 two-optional-parameter read-only list tool with an output schema, the description covers purpose, returned fields, and the critical `name` = `vserver` linkage that no structured field conveys. Nothing needed to call it correctly is missing.

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 100% and both parameters (page, limit) are fully documented with defaults and ranges in the schema. The description says nothing about paging, so it adds no meaning beyond the structured field definitions; baseline 3 applies.

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 ('List the webhosting packages (virtual servers) on the account') and then enumerates the returned fields, so the agent knows exactly what it gets back. It is clearly distinguishable from siblings like list_domains or list_mysql because it names the webhosting/vserver entity.

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 second sentence gives strong implicit routing: run this to discover the `name` value that the mail, MySQL, cron and SSL tools take as `vserver`. It does not state explicit exclusions or when to prefer a sibling, but the downstream-consumption context is concrete.

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