servicebus_peek_messages

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

No annotations provided, so description covers read-only nature, max_count cap, session behavior, and return of bodies/metadata. Could mention rate limits or pricing implications, but sufficient.

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?

Five concise sentences front-load the purpose, with no redundant information. Every sentence adds value.

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 complexity, description covers key aspects: read-only operation, parameter constraints, session handling, and alternative tool. Output schema exists but specifics of return values are briefly mentioned.

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%, but description compensates for max_count (capped at 100) and session_id (optional, explained). Namespace and queue are required but not further described beyond schema.

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 it peeks at messages non-destructively, and distinguishes from siblings like servicebus_peek_messages_to_file by noting when to use the alternative.

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?

Explicitly states it is read-only, non-destructive, and advises using servicebus_peek_messages_to_file for large messages. Session handling behavior is also explained.

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