Update Plone Content

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

No annotations, so description must disclose behavior. It notes the ability to update metadata or block structure and mentions a potential 400 error for preview images. However, it omits authentication requirements, reversibility, or side effects of block replacement.

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?

Two sentences plus an example, no fluff. Front-loaded with purpose. Every sentence contributes meaning.

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 6 parameters and no output schema, the description covers main use cases and references sibling tools for complex operations. Lacks details on return values but is adequate for an agent with complementary tools.

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 100%, but description adds context: the dual capability of updating metadata or block structure, and a specific example. AdditionalFields gets extra guidance on preview image errors. Adds moderate value beyond schema.

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?

Description clearly states 'Modifies an existing content item in Plone,' specifying a verb and resource. It distinguishes from siblings by recommending alternative tools for different tasks.

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?

Explicitly tells when to use other tools (e.g., plone_create_blocks_layout for complex block updates, plone_add_single_block and plone_update_single_block for smaller changes) and instructs not to edit block structure directly.

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