security-set-item-protection

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true), so the bar is lower. The description adds real value on top by defining what protection actually does to the item — blocks deletion and renaming — and clarifies the independence from the editing lock, which prevents a common misuse. Auth requirements and persistence details remain unstated.

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 tight sentences with zero waste, purpose front-loaded and the sibling disambiguation following immediately. Every clause earns its place.

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 7-parameter mutation tool with no output schema and full schema description coverage, the description covers purpose, scope, and sibling routing adequately. It leaves return behavior to the schema and doesn't discuss permission requirements, a minor gap but not a blocking one.

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 the schema already documents id, path, database, action, fields, full, and passThru. The description adds no parameter-level meaning beyond that, which makes the baseline 3 the correct score rather than a higher one.

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?

States a specific verb (protects/unprotects), the resource (a Sitecore item), and precisely what is being protected against (deletion and renaming). It explicitly distinguishes itself from the adjacent sibling security-set-item-lock, so an agent can route between the two without inspecting schemas.

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?

Names the alternative tool (security-set-item-lock) and the concept that separates them (the editing lock), giving clear context for when to pick this one. It stops short of full when-not guidance (e.g., required permissions or when protection should be avoided), so it isn't a 5.

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