get-vhost-permissions

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

Annotations already indicate readOnlyHint=true, so the description does not need to cover safety. However, it also does not add behavioral details such as what the returned permissions include (e.g., users, configure/write/read patterns) or any constraints like authentication requirements. The description adds minimal value beyond the annotations.

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, concise sentence of seven words that efficiently conveys the tool's purpose without any unnecessary information. It is front-loaded with the action and scope.

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 list tool with one parameter and no output schema, the description is mostly complete. It explains what the tool does and what the parameter means. However, it could benefit from mentioning what the response looks like (e.g., a list of permissions with user and permission levels) but is not strictly required given the tool's simplicity.

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 input schema has one required parameter 'name' with 0% documentation coverage. The description provides meaningful context by stating that 'name' refers to 'a given virtual host', which compensates for the lack of schema descriptions. This is sufficient for the agent to understand the parameter's role.

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 clearly states the action ('List all permissions') and the target resource ('for a given virtual host'). It uses a specific verb and resource, and it distinguishes itself from sibling tools like 'list-permissions' and 'list-user-permissions' by specifying the scope.

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 implies usage when a virtual host's permissions are needed, but it does not explicitly state when to use this tool over alternatives (e.g., 'list-permissions') or provide any exclusion criteria. The context from the tool name and siblings suggests the purpose, but explicit guidance is missing.

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