dw_paragraph_create

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

The description discloses that paragraphs are ordered ascending via the sort field and hints at future reordering, but lacks details on error handling (e.g., invalid pageId or itemType), permissions, or side effects. Since no annotations are provided, the description carries full burden, and while it adds context beyond the schema, it is insufficient for a complete behavioral understanding.

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 concise with three short sentences: the first stating purpose, the second giving next-step guidance, and the third explaining sort ordering. No extraneous information, and the structure is easy to parse.

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?

Given 4 input parameters, no output schema, and sibling tools, the description adequately covers the creation step and directs to dw_paragraph_set_fields for content population. However, it does not describe the return value (likely the paragraph ID) or possible errors, making it incomplete for an agent to fully understand the tool's behavior.

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 50% (pageId and itemType have descriptions, sort and active do not). The description adds meaning to the sort parameter by explaining the ordering convention and suggesting values. However, it does not explain the active parameter or its defaults beyond the schema, and it does not fully compensate for the missing schema descriptions of all parameters.

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 tool creates a new paragraph on a DynamicWeb page, using 'Create a new paragraph' and specifying the mechanism (ParagraphSave) and item type. It differentiates from sibling tools like dw_paragraph_set_fields by indicating it is for creation only and that field population is a separate step.

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 explicit guidance to use dw_paragraph_set_fields after creation for populating content fields, which helps the agent understand the workflow. It also explains the sort parameter's ascending order and suggests using increments of 100 for easy re-ordering, but does not specify when not to use this tool or mention alternatives for similar operations.

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