Create Plone Content

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

No annotations are provided, so the description carries the full burden. It discloses basic creation behavior but lacks details on side effects (e.g., whether it overrides existing content), required permissions, or error scenarios. The mention of preview_image_link suggests some error handling, but overall transparency is minimal.

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: two sentences plus an example. It front-loads the purpose and key usage instruction. It could be slightly more structured but is efficient and free of fluff.

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 8 parameters, no output schema, and no annotations, the description covers basic creation and block-based content. It lacks details on return values, error handling, or authentication needs. For a create tool with multiple nested object parameters, it is minimally complete but not rich.

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 all 8 parameters are documented. The description adds a usage example and mentions using blocks and blocks_layout for complex content, but does not provide significant new meaning beyond the schema. Baseline 3 is appropriate.

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 explicitly states 'Creates a new content item (e.g., a page or news article) in Plone' and differentiates from the sibling tool plone_create_blocks_layout by indicating it should be used first for block-based content. The verb 'Creates' and resource 'content item' are clear.

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 a clear when-to-use: for adding complex block-based content, first call plone_create_blocks_layout then this tool. An example is given. However, it does not explicitly state when not to use or mention alternatives like update/delete tools, but the context with sibling tools makes it implicit.

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