presentation-remove-placeholder-setting

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description's 'Removes' is consistent with that. However, it adds nothing beyond the annotation: no statement of irreversibility, no note that the removal is permanent or that the setting can be re-added, and no auth/permission context for a destructive mutation.

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 wasted words, but it is thin for a 7-parameter destructive tool. Conciseness is achieved at the cost of any useful framing, so it sits at minimum viable rather than strong.

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, 7-parameter mutation with no output schema and only hint-level annotations, the description should say more: which of key vs uniqueId identifies the setting, the id/path resolution rule, and that finalLayout selects shared vs final layout. None of that is in the prose, leaving the agent dependent on the schema alone.

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%, with each of the 7 parameters documented in-schema, including the id-or-path alternative and the finalLayout layout scope. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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: removing a placeholder setting from an item. It is unambiguous about what is deleted, but it offers no differentiation from close siblings like presentation-remove-rendering, presentation-remove-rendering-parameter, or presentation-remove-placeholder-setting's counterpart operations.

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 other presentation-removal tools, nor any prerequisites (e.g., that the setting must exist, or which layout scope applies). The agent must infer usage entirely from the name.

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