presentation-remove-rendering

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether removal is irreversible, whether one or many renderings are affected, whether a layout version must be published, or what permissions are needed. For a destructive mutation it contributes no behavioral 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?

A single front-loaded sentence with no filler or redundancy. It is appropriately compact, though the brevity shades into under-specification rather than distilled precision.

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?

This is a destructive eight-parameter mutation with no output schema and only destructiveHint from annotations. A one-sentence description leaves consequences, scope, and interaction with layout/finalLayout behavior unexplained, which is not enough context for an agent to call it safely.

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 description coverage is 100%, so all eight parameters including uniqueId, finalLayout, and dataSource are already documented in the schema; baseline 3 applies. The description adds no filtering syntax or default behavior beyond what the schema states, and its plural wording slightly obscures whether uniqueId targets a single rendering.

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 states a specific verb and resource ('Removes renderings from an item'), so the agent knows this deletes presentation renderings rather than layout or placeholder settings. However, it does not differentiate itself from close siblings such as presentation-remove-rendering-parameter or presentation-reset-layout, and the plural 'renderings' mildly clashes with the required single uniqueId in the schema.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent gets no help deciding between this tool, presentation-remove-rendering-parameter, or presentation-reset-layout for removing presentation data.

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