listVhosts

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

With no annotations provided, the description must disclose behavioral traits. It only states 'List all vhosts/endpoints', adding minimal context beyond the tool name (that it lists all). It does not disclose pagination behavior, permission requirements, or any side effects.

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 a single sentence with no fluff, but it contains a stray closing parenthesis and the phrasing is slightly awkward. Still, it is appropriately sized for a simple listing tool.

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 a similar sibling tool 'listServiceVhosts', the description lacks necessary context to distinguish the global scope of this tool. It also does not mention any filtering or ordering behavior. The presence of an output schema covers return values, but overall contextual information is sparse.

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 tool accepts zero parameters, so the schema already describes all inputs. The description adds no parameter-specific information, which is unnecessary here. Baseline 4 is appropriate.

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 uses a specific verb 'List' and resource 'vhosts/endpoints', clearly indicating the tool's function. However, it does not differentiate from the sibling tool 'listServiceVhosts', which may also list vhosts but scoped to a service.

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 description provides no guidance on when to use this tool versus alternatives like 'listServiceVhosts'. It lacks any contextual information about use cases or exclusions.

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