list-bindings

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

Annotations already state readOnlyHint=true and openWorldHint=true, but the description adds no additional behavioral context such as whether pagination is supported, rate limits, or what constitutes 'all bindings' (e.g., system or user-created).

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?

A single, front-loaded sentence with no unnecessary words. Every word contributes meaning, making it highly efficient.

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 parameterless, read-only listing tool with clear annotations, the description is largely complete. However, it omits what the output contains (e.g., list of binding objects) and any edge cases (e.g., empty cluster). Missing this context slightly reduces completeness.

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 no parameters (100% coverage), so the description does not need to add parameter details. Baseline 4 applies; no value added beyond the schema, but no deficiency.

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 'List all bindings in the RabbitMQ cluster' uses a specific verb ('List') and clearly defines the resource ('bindings') and scope ('all', 'cluster'), distinguishing it from sibling tools that filter bindings by exchange, queue, or vhost.

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 using this tool for a global listing, but lacks explicit guidance on when to choose it over filtered variants (e.g., list-bindings-exchange-exchange). No when-not-to-use or alternative recommendations are provided.

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