List RabbitMQ Vhost

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that — no note on result size, ordering, pagination, or whether the list is scoped to a namespace.

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 but not concise in a useful sense — it is under-specified rather than economical. The single fragment duplicates the title verbatim, so no sentence earns its place beyond what structured fields already convey.

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-parameter list tool with no output schema and no annotation covering return shape, the description should say whether the response is scoped, paginated, or ordered. None of that is present, leaving the agent unable to predict the result beyond 'a list of vhosts'.

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% at the top level: the required 'cluster' parameter has only a pattern and length constraint with no explanation of what a cluster identifier means here. The reusable namespace ref does carry a description, but the description text itself explains neither parameter nor how the optional namespace narrows the listing.

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?

No when-to-use guidance is given: nothing says when to choose this over rabbitmq_vhost_get or how the required cluster parameter affects selection. The agent must infer that listing all vhosts precedes fetching one.

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