Get webhosting server info

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that — no indication that data is fetched live from the server, no note on failure modes for an unknown vserver, and it spends its only sentence restating return contents.

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?

It is short and contains no filler words, which is good. However, the content is a comma-separated field dump that duplicates the output schema rather than front-loading the tool's purpose, so the brevity buys little.

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?

An output schema exists, so the description did not need to enumerate return fields — yet that is essentially all it does. For a tool with one required argument and open-world reads, it omits the purpose, the typical workflow position, and any caveats, leaving clear gaps.

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% and the single parameter is documented with format hints and an example ('example.com') plus a reference to list_webhostings. The description contributes no additional meaning about the vserver argument, so 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?

The description names the resource ('Server details for a webhosting') and enumerates what is returned, so an agent can grasp the topic. But it is a bare noun phrase with no verb, and it never distinguishes this from siblings such as list_webhostings or get_domain, which also return hosting-related data.

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?

There is no when-to-use guidance: no statement of the scenario that calls for server info, no prerequisite that a webhosting must exist or be listed first. The only pointer to list_webhostings lives in the schema, not the description.

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