servicebus_peek_subscription_messages_to_file

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

With no annotations, the description carries the full burden. It discloses non-destructive nature, file writing, and session behavior. However, it omits details like file overwrite policy, error handling, and any rate limits, leaving some behavioral aspects unclear.

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 two short paragraphs that front-load the core purpose. Every sentence adds value without redundancy or fluff.

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 moderate complexity and presence of an output schema, the description covers the essential aspects: non-destructive peek, file saving, and session handling. It could mention that the output file is JSON, but overall it is sufficiently complete for effective use.

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. It explains output_file (saves bodies as JSON), max_count (peek count default 10), and session_id (optional, with session-release behavior). However, it does not describe namespace, topic, or subscription beyond their names, which are needed for full clarity.

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 from an Azure Service Bus topic subscription and saves bodies to a file. It distinguishes itself from sibling tools like servicebus_peek_subscription_messages by highlighting the file-saving behavior, making the purpose specific and unambiguous.

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 explains when to use this variant (when message bodies may be large to avoid filling context window) and covers session handling. It lacks explicit when-not-to-use guidance but provides sufficient context for appropriate selection among siblings.

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