servicebus_peek_messages_to_file

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

Describes key behaviors: non-destructive peek, writing bodies to file, returning only metadata in context, session handling (accept and release). No annotations provided, so description carries full burden. Missing details like error handling or file overwrite behavior, but covers primary traits well.

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?

Description is 6 sentences, front-loaded with the primary action and key differentiator. No redundant or unnecessary information. Each 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 5 parameters, no annotations, and presence of an output schema (though not detailed), the description covers the tool's purpose, usage context, and key behaviors. Could mention output file format in more detail or potential file size implications, but sufficient 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 description adds meaning. Explains output_file usage (writes bodies as JSON keyed by sequence number) and session_id behavior. However, namespace and queue parameters are not elaborated beyond their names, but their purpose is self-explanatory given tool context.

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?

Description clearly states the tool peeks non-destructively at messages and saves bodies to a file, distinguishing it from the sibling servicebus_peek_messages which does not save to file. It specifies the action, resource, and key differentiator (large message bodies).

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 when to use this variant (when message bodies may be large to avoid filling context window). Provides guidance for session-enabled queues: either provide session_id for a specific session or omit to accept the next available session, which is then released.

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