rabbitmq_broker_list_policies

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

The description lacks any behavioral disclosure beyond the basic operation. There is no mention of idempotency, safety (though likely read-only), error conditions, permissions, or rate limits. With no annotations, the agent must infer behavior from the name alone.

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 that directly conveys the tool's purpose. Every word is necessary; there is no redundancy or extraneous information.

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 tool's simplicity and the presence of an output schema, the description is insufficiently complete. It does not mention any prerequisites, pagination, or behavior when the vhost does not exist. Additionally, it fails to differentiate from the closely related rabbitmq_broker_get_policy tool.

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 only parameter 'vhost' has no schema description (0% coverage). The description merely says 'in a virtual host,' which adds no meaningful explanation beyond the parameter title. For a tool with zero schema descriptions, the description should compensate by explaining the parameter's role, default behavior, or format.

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 states 'List all policies in a virtual host,' using a specific verb ('List') and resource ('policies') with a clear scope. It effectively distinguishes this tool from sibling listing tools (e.g., list_queues, list_exchanges) by naming a different resource type.

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 guidance is provided on when to use this tool versus alternatives, such as rabbitmq_broker_get_policy for a single policy. There are no criteria for selection or exclusions.

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