item-service-edit-item

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

No annotations are provided, so the description carries full burden. 'Edit' implies a mutation operation, but the description doesn't disclose important behavioral traits: whether this requires specific permissions, if changes are reversible, what happens to validation or workflow states, or how conflicts are handled. For a mutation tool with zero annotation coverage, this is inadequate.

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 extremely concise at just 7 words, front-loaded with the core purpose. There's zero wasted language, though this conciseness comes at the cost of completeness.

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 mutation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what constitutes a valid edit, what fields can be modified, what the response looks like, or any error conditions. The context demands much more information than provided.

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?

With 0% schema description coverage and 3 parameters (including nested objects), the description provides no parameter information beyond what's implied by 'by its ID'. It doesn't explain what 'data' should contain, what 'options' controls, or how the parameters interact. The description fails to compensate for the complete lack of schema documentation.

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 action ('Edit') and resource ('a Sitecore item by its ID'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'item-service-update-item' (if present) or explain how it differs from other item modification tools in the list.

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. With many sibling tools available (like 'item-service-create-item', 'item-service-delete-item', 'item-service-get-item'), there's no indication of when editing is appropriate versus creating new items or using other modification methods.

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