Remove a website page

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

Annotations already declare destructiveHint=true, so the description's mention of deletion is redundant. The added value is the constraint that the home page cannot be removed, which is a behavioral trait. No other traits (e.g., permissions, irreversibility) are disclosed. No contradiction with annotations.

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 very concise: two short sentences with no extraneous words. It is front-loaded with the action. However, it could benefit from including brief param guidance without becoming verbose.

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 no output schema, no parameter descriptions, and a simple action, the description fails to provide enough context. It doesn't explain the result (e.g., what happens to dependent files), required permissions, or how to undo. The exception about home page is helpful but insufficient.

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?

The schema has 2 required parameters (slug, project) with zero description coverage. The description only mentions 'by slug' but does not explain what slug or project mean, nor their format or constraints. It adds minimal value over 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?

The description clearly states the verb 'Delete' and the resource 'sub-page (by slug) and its rendered file', matching the title. It also notes the exception for the home page, but doesn't differentiate from sibling deletion tools like remove_test_page or remove_product.

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 provides no explicit guidance on when to use this tool versus alternatives. It only mentions that the home page cannot be removed this way, which implies an alternative exists but does not name it. No prerequisites or context of use are given.

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