delete_content

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only mentions that confirmation is required, but fails to state that deletion is irreversible, any cascading effects, authentication needs, or return behavior. The destructive nature is implied by the name but not elaborated, leaving a significant gap for a mutation tool.

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 two short sentences, with every word adding value. 'Deletes a Plone object' states the action, and 'Confirmation required' conveys a critical prerequisite, with no redundancy or padding.

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?

The tool is a destructive operation with 4 parameters, no annotations, and no output schema, yet the description only provides the basic action and confirmation flag. It omits authentication context, error handling, and post-deletion behavior, making it incomplete for reliable invocation.

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 0%, so the description must compensate by explaining parameter meaning. It only hints at the 'confirmed' parameter by stating confirmation is required, but gives no meaning for content_url, token, or cookie. This is insufficient for a 4-parameter tool.

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 verb 'Deletes' plus the resource 'Plone object' clearly states the tool's function. It is distinct from siblings like create_content and patch_content, and the confirmation requirement adds specific scope.

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 clearly implies use when a Plone object needs to be removed, which distinguishes it from the create and patch siblings. However, it does not explicitly state when not to use it or mention any alternatives, so it falls short of a 5.

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