Get RabbitMQ Vhost

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context at all — no note on error behavior for a missing vhost, required permissions, or whether the optional namespace scopes the lookup — so it contributes nothing beyond structured fields.

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 text is short but only because it is under-specified rather than economical; it is a verbatim echo of the title. There is no front-loaded scope, constraint, or routing information to reward the 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?

This is a simple single-resource read with annotations covering the safety profile and no output schema to explain, so the bar is low. Even so, the description supplies zero of the small amount of information an agent needs — namely that 'vhost' selects the record, 'cluster' selects the target, and 'namespace' is an optional scope.

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 0%: only the referenced NamespaceName definition is documented, while the required 'cluster' and 'vhost' parameters have bare types and patterns with no explanation. The description does not compensate — it never explains what a vhost identifier looks like, what the cluster pattern refers to, or when the optional namespace should be supplied.

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?

Tautological: description restates name/title.

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 guidance on when to use this tool versus rabbitmq_vhosts_list, nor on prerequisites such as whether the vhost must already exist. The name weakly implies a single-item fetch by identifier, but nothing in the description confirms or excludes anything.

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