authoring-create-item

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context (returns the created item, parent must be a GUID) but says nothing about auth requirements, failure modes, or what happens when the item already exists.

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 dense sentences, front-loaded with what the tool does and immediately followed by the key non-obvious constraint and the pointer to the helper tool. 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 create tool with no output schema, the description covers the action, the return value, and the GUID constraint on parent. It stops short of describing error behavior or versioning/language interactions, but the essentials for a correct call are present.

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 detailed guidance for all six parameters including name character restrictions and template ID format. The description adds the parent-GUID constraint but otherwise defers to the schema, so the baseline of 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?

States a specific verb+resource ('Creates a Sitecore item from a template') and the API channel ('Authoring and Management API') and return behavior. Beyond that, it distinguishes itself from item-service-create-item by naming authoring-get-item as the path-resolution helper.

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?

Gives a concrete prerequisite: parent must be a GUID, and routes the agent to authoring-get-item to resolve a path first. It does not explicitly contrast with item-service-create-item, which is a plausible alternative for item creation.

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