rabbitmq_broker_get_messages

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

With no annotations, the description carries the transparency burden. It discloses that messages are requeued by default and explains the ackmode behavior. This is good, but it lacks details on potential side effects, limits, or rate limits, which would further enhance transparency.

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 concise, with only two sentences plus a line for ackmode details. It front-loads the main purpose and uses a clear structure. No unnecessary words or redundancy.

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?

Despite lacking detail on what happens with an empty queue or how count works, the description covers the core behavior well. Since an output schema exists, return value documentation is not needed. The tool is simple, and the description is mostly adequate.

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%, so the description must add parameter meaning. It explains the ackmode parameter and its values, adding value beyond the schema. However, it does not describe count, queue, or vhost, leaving three parameters with only schema names and defaults. Partial compensation.

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 tool's purpose: to peek at messages in a queue without consuming them, using the verb 'peek' and specifying the resource 'messages in a queue'. It distinguishes itself from consuming by emphasizing non-consumption and requeueing. This is specific and informative.

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 provides clear usage context: use this tool to peek at messages, not to consume them. It explains the ackmode parameter with two modes (peek vs consume). However, it does not explicitly list alternative tools or state when not to use this tool, missing some exclusion guidance.

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