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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the mutation/safety profile is covered structurally. The description adds nothing behavioral beyond that: no mention of permission requirements, no note that position insertion can shift existing paragraphs, and no indication of what is returned on success. For a mutation tool with conditional per-type requirements, that is a meaningful gap.

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?

It is short and front-loaded, but the first sentence duplicates the title and the second sentence largely repeats it. The trailing "| context: id, type" is an unexplained fragment that consumes space without conveying meaning to an agent. Concise, but not every element earns its place.

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 7 parameters, four block types each having different required fields, no output schema, and no annotations covering the mutation details, the description should explain the per-type requirements and insertion behavior. Instead it offers nothing beyond a one-line restatement of the title. An agent would have to reverse-engineer calling conventions entirely from the schema.

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%, so every parameter including the type enum and the conditional content/embedUrl/originalThumbnail fields is already documented in the schema. The description contributes nothing beyond it, and the "context: id, type" fragment merely echoes the schema's required list. Baseline 3 is appropriate when the schema does all the work.

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 definition states a verb and resource ("Create paragraph") and adds the parent scope ("under a CMS article"), so the basic operation is identifiable. However, it does not distinguish this generic paragraph creator from the many sibling paragraph creators (cms_create_video_paragraph, cms_create_map_paragraph, cms_create_event_paragraph, etc.), and it never mentions that this tool handles text/photo/quote/embed blocks. The purpose is only minimally viable given how crowded the sibling space is.

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?

"Guidance: Create one paragraph under a CMS article" is a restatement of the purpose, not usage guidance. There is no statement of when to choose this tool over the type-specific siblings, no prerequisites, and no exclusions. The cryptic "context: id, type" fragment does not tell an agent anything actionable about selection.

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