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

Annotations only declare readOnlyHint=false and destructiveHint=true. The description adds genuinely new behavioral context: the collection stores and can be read back, and creating one does not publish a page per item. That clarifies the blast radius beyond the annotation, though it never explains what makes the operation destructive.

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 purpose and jargon definition, then the return value, then the publishing caveat. No filler and no repetition of the schema.

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?

With no output schema, the description correctly states the key return value (each field's key) and explains the downstream publish path. The only gap is that siteId is left unexplained and the destructiveHint is never accounted for.

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 67%, so the schema already documents name, the fields array, and its label/options semantics; siteId is undocumented in both places. The description adds only marginal parameter meaning by noting that returned field keys feed create_item, which is a reasonable baseline-3 contribution.

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 ("Create a CMS collection") and immediately defines the concept for non-experts with concrete examples (Posts, Team, Testimonials). It also implicitly distinguishes itself from create_item by describing the downstream relationship, so an agent can place it in the workflow without opening the 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?

The description gives clear workflow context: the returned field keys are what create_item expects, and content only becomes visible via add_section. It stops short of an explicit when-to-use/when-not statement or naming list_collections as the read alternative, but the sequencing guidance is strong.

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