security-lock-item-by-path

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Lock a Sitecore item') but fails to describe key behavioral traits: what 'locking' entails (e.g., prevents edits, may require admin rights), the effect of the 'force' parameter (overriding other users' locks), or potential side effects (e.g., error if item doesn't exist). This leaves significant gaps for a mutation tool.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero waste, making it easy to parse quickly.

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 the complexity of a mutation tool (locking items) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral outcomes (e.g., what happens on success/failure, return format), usage context (e.g., permissions, alternatives), and error handling, making it inadequate for safe and effective use by an AI agent.

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 input schema has 100% description coverage, fully documenting all four parameters (path, force, passThru, database) with clear descriptions. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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 states the verb ('Lock') and resource ('a Sitecore item by its path'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'security-lock-item-by-id', which performs the same function but uses an ID instead of a path, leaving room for potential confusion.

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 provides no guidance on when to use this tool versus alternatives, such as 'security-lock-item-by-id' (which locks by ID instead of path) or other security tools like 'security-protect-item-by-path'. It also lacks information about prerequisites, like required permissions or item states, leaving usage context unclear.

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