deletePage

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

The description lacks any behavioral disclosure beyond the basic action. With no annotations provided, it fails to address critical aspects like permissions required, whether deletion is permanent or reversible, impact on linked content, or error conditions. For a destructive operation, this is a significant gap.

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 maximally concise with a single, direct sentence that states the core functionality without unnecessary words. Every element ('Delete', 'a page', 'from AEM') contributes essential information.

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 destructive tool with 2 parameters, 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't address safety concerns, parameter meanings, expected outcomes, or error handling that are crucial for proper tool 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?

With 0% schema description coverage for both parameters, the description provides no information about what 'pagePath' should contain or what the 'force' boolean does. It doesn't explain path format expectations, what 'force' overrides, or any parameter constraints beyond what's in the bare 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?

The description clearly states the action ('Delete') and resource ('a page from AEM'), making the purpose immediately understandable. It distinguishes from siblings like 'deleteAsset' or 'deleteComponent' by specifying 'page', but doesn't explicitly contrast with similar tools like 'deactivatePage' or 'unpublishContent'.

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 on when to use this tool versus alternatives. With siblings like 'deactivatePage', 'unpublishContent', and 'deleteVersion', there's no indication of prerequisites, consequences, or appropriate contexts for deletion versus other page-modification operations.

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