get-queue-messages

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

The description contradicts annotations: annotations set readOnlyHint=true implying no side effects, but the tool can actually consume and delete messages (depending on ackmode). The description does not disclose this destructive potential, nor does it mention behavior like message ordering or blocking. This is a clear annotation contradiction.

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 extremely concise (one sentence) but at the cost of necessary information. It lacks structure and fails to add value beyond the tool name. Effective conciseness would require more context in the same space.

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?

Without an output schema, the description should explain return values (e.g., message payloads, metadata). It does not. The tool is moderately complex, and the description leaves agents with little understanding of inputs, behavior, or outputs. It is severely incomplete.

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 coverage is 0%, so the description must compensate. However, it provides no parameter information. It does not explain the meaning of ackmode, count, encoding, truncate, or requeue. For a tool with 7 parameters, this is a major gap.

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 'Get messages from a queue' clearly states the verb and resource. However, it does not distinguish this tool from siblings like get-queue, get-queue-bindings, or get-queue-unacked, which also involve queues. The purpose is clear but lacks differentiation.

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. The description does not mention prerequisites, typical use cases, or when other tools like list-queues or get-queue might be more appropriate. Agents are left without decision support.

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