aem_configuration_delete

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. 'Delete' does signal mutation/destructiveness, but the description does not mention permanence, required permissions, effects on runtimes or instances, or whether the deletion targets all specified instances/aliases.

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 one short declarative sentence with no filler or redundancy. It is front-loaded with the essential action and resource, which is ideal for conciseness even if other dimensions lack depth.

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?

With no annotations, no output schema, and a one-sentence description, the tool is under-specified for an agent deciding whether deletion is appropriate or what it will affect. The presence of optional aliases and instances fields raises questions about targeting that the description does not address.

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%, with each parameter having some description in the schema. The tool description itself adds no parameter-level meaning, so the baseline of 3 applies: the schema does the heavy lifting and the description does not need to compensate.

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 uses a specific verb ('Delete') and a clear resource ('an OSGi configuration'), so an agent can tell this is a destructive configuration operation. It differentiates from list/get/create/update, though it doesn't explicitly contrast with aem_configuration_unbind, making 5 slightly too strong.

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 is provided about when to use this tool instead of related ones such as aem_configuration_unbind, aem_configuration_update, or aem_configuration_create. The description only states what it does, not the conditions or prerequisites for invoking it.

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