fabric_delete_eventstream

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

The description repeats the annotation's destructiveHint with 'Destructive' but adds no further behavioral context. Annotations already signal destruction, so the description adds no value beyond highlighting the obvious.

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 very concise, but 'Destructive' is redundant given the annotation and the verb 'Delete'. It could be restructured to include useful context while remaining brief.

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?

For a destructive operation without an output schema, the description does not explain side effects, reversibility, or prerequisites. Additional context beyond the bare action is needed for safe tool invocation.

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 100%, with clear parameter descriptions for id and workspace. The description does not add any additional parameter guidance, so it meets the baseline for high coverage.

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 'Delete an eventstream' clearly states the verb and resource, distinguishing it from sibling tools like fabric_create_eventstream or fabric_list_eventstreams. However, it lacks any additional detail about scope or conditions.

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. There is no mention of prerequisites, when not to use, or relationships to other operations.

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