preview_delete_view

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'Preview deleting' but does not explain whether this is non-destructive, what it returns, or what side effects it may have. The term 'preview' is ambiguous without further context.

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 a single concise sentence with no filler. While it is under-specified in content, it is appropriately sized and front-loaded for a simple tool description.

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 that this is a preview operation with no output schema and minimal annotations, the description is incomplete. It does not explain what 'preview' entails, what the agent should expect as output, or how it relates to delete_view. Critical context is missing.

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?

The schema has zero description coverage for its two parameters (listId, viewId), and the description does not mention them at all. The tool provides no additional meaning beyond the raw schema, failing to compensate for the missing parameter documentation.

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 identifies the resource (SharePoint list view) and the action (preview deleting), making the basic purpose understandable. However, it does not explicitly distinguish this from the sibling delete_view tool, which is a minor omission.

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?

There is no guidance on when to use this tool versus the actual delete_view or other preview tools. The 'preview' prefix implies a dry-run, but the description does not state this or any recommended workflow.

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