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

Annotations already supply readOnlyHint=false and destructiveHint=true. The description adds genuinely useful behavior the annotations do not carry — items publish to live by default and draft:true suppresses that — but it never explains the response, permissions, or what 'destructive' means for a create (e.g. duplicate slugs).

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 short, front-loaded sentences with no filler; the core action comes first and each following sentence adds a distinct piece of information.

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 5-param create tool with a nested object, no output schema, and zero schema descriptions, the definition covers the hardest part (field keying and publish default) but omits slug behavior, identifier requirements, and any hint at the returned item.

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 0%, so the description must compensate. It does explain that `fields` is keyed by field keys from list_collections and clarifies `draft` semantics plus its default, but slug, siteId, and collectionId — including three required params — remain unexplained in both schema and description.

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 ('Add an item to a CMS collection'), which cleanly separates it from siblings like create_collection, create_page, and update_item without the reader opening a schema.

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?

Usage is implied (add new, not modify existing) and it usefully cross-references list_collections for field keys, but it never states when to prefer update_item over create_item, nor any prerequisite ordering (site/collection must exist).

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