delete_page

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

With no annotations provided, the description carries full burden. It discloses the destructive nature ('Permanently delete', 'cannot be undone') and required authorization scopes. This is adequate for a simple delete tool. No contradictions exist.

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 sentences that deliver essential information without redundancy. The first sentence states the action and scope, the second adds irreversibility and permissions. Every word earns its place.

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 simple delete tool with one parameter and no output schema, the description covers the key aspects: action, irreversibility, and required permissions. It could be improved by mentioning the expected return value or confirmation behavior, but it is sufficient for an agent to use correctly.

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 baseline is 3. The description adds no new information beyond what the schema already provides for 'page_id'. The schema description already states 'The numeric Shopify page ID or GID to delete.' The tool description repeats this concept without elaboration.

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 tool's action: 'Permanently delete an online store page.' It distinguishes from sibling tools that delete other entities (e.g., delete_product, delete_theme) by targeting pages specifically. The verb 'delete' plus resource 'page' is unambiguous.

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 important usage context: the operation is permanent ('cannot be undone') and requires specific access scopes ('write_content or write_online_store_pages'). This helps the agent decide when it's appropriate to use. However, it does not explicitly contrast with alternatives or state when not to use, which could be improved.

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