authoring-delete-item

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

Annotations already declare destructiveHint=true, so the safety profile is known. The description adds materially more: the default recycle-bin behavior with restorability, the irreversibility of permanently=true, and the cascade deletion of descendants — exactly the behavioral context annotations cannot express.

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?

Three tight sentences, front-loaded with the core action, then the default/permanent distinction, then the cascade warning and targeting constraint. No filler.

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 mutation with no output schema, the description covers reversibility, cascade scope, and argument selection. It omits auth/permission requirements and failure behavior (e.g. locked or published items), which leaves a modest gap but nothing an agent would likely get catastrophically wrong.

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%, so parameters are already documented; baseline would be 3. The description adds a real constraint the schema does not enforce — 'Supply exactly one of id or path' — which is genuinely useful selection logic beyond the per-field 'supply this or path' text.

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 and resource ('Deletes a Sitecore item') and names the API surface it operates over. It does not differentiate itself from the sibling item-service-delete-item, so an agent scanning both cannot tell which is preferred without opening 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?

The description implies usage (single-item deletion, choose id or path) but never states when to prefer this tool over item-service-delete-item, nor any prerequisite such as required permissions or item-lock state. Usage is implied rather than guided.

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