apex_delete_page

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

Annotations already indicate destructive and non-read-only behavior. The description confirms the destructive nature but adds no further behavioral context (e.g., irreversibility, cascade effects, or permission requirements). It does not contradict 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 a single, efficient sentence that immediately states the operation, front-loading the core purpose. It contains no filler or redundancy.

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 a simple two-parameter operation, an output schema, and annotations covering destructive behavior, the description is sufficient for the agent to understand the tool's primary effect. It does not elaborate on potential side effects, but that detail is not critical given the structured context.

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%, so parameters app_id and page_id are fully described in the schema. The description does not add additional parameter meaning beyond what the schema already provides, making a baseline score of 3 appropriate.

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 the resource (a page). It distinguishes from sibling tools like apex_delete_app or apex_delete_region by being specific to 'page' deletion, aligning with the tool name apex_delete_page.

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 implies usage for deleting a page but provides no explicit when-to-use, when-not-to-use, or alternative tool references. The constraint about page 0 is in the schema, not the description, so within the description itself, guidance is limited to the implied context.

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