Delete Plone Content

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

States 'permanently deletes', which is the key behavioral trait, but lacks details on side effects (e.g., recursive deletion for folders), permission requirements, or undo capabilities. No annotations were provided to supplement.

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: first explains action and resource, second provides a concrete example. No redundant information; each sentence 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?

For a tool with one parameter and no output schema, the description is mostly complete. However, explicitly stating that deletion is irreversible would improve completeness, especially given the destructive nature.

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% with path described. Description adds an example showing exact usage format, which clarifies the parameter expectation beyond the 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 the verb 'permanently deletes', the resource 'content item', and the method 'using its path'. This distinguishes it from sibling tools like plone_get_content or plone_update_content.

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?

No guidance on when to use versus alternatives (e.g., workflow transitions instead of deletion) or when not to use. For a destructive operation, prerequisites or cautionary notes are absent.

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