servicebus_peek_subscription_dlq_to_file

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

No annotations, but description discloses non-destructive read, file output format (JSON keyed by sequence number), and that only metadata is returned. Could mention file overwrite behavior or permissions, but covers main traits.

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?

Two sentences, front-loaded with purpose and key details, no extraneous information.

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?

Covers purpose, action, and output. With output schema present, return values not needed. Missing file overwrite and error handling details, but sufficient for a peek tool.

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?

0% schema coverage, but description adds meaning for output_file (write as JSON) and implies max_count limits peek count. Other parameter names are self-explanatory, but no further details provided.

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 subscription dead letter queue messages and saves bodies to a file, distinguishing it from siblings like servicebus_peek_subscription_dlq (no file) and servicebus_peek_dlq_to_file (queue DLQ).

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?

Implied usage for inspecting subscription DLQ and saving bodies, but no explicit guidance on when not to use or alternatives beyond what sibling names suggest.

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