delete_landing_page

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

Since no annotations are provided, the description carries full burden. It discloses: permanence, immediate URL inaccessibility, analytics retention, authentication via API key, max 10 concurrent requests, respect for read-only/dry-run modes, and 404 error response. This goes beyond basic expectations.

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?

Description is well-structured with a strong lead sentence, followed by side effects, alternative usage, authentication/limits, and a clear Args/Returns section. It is slightly verbose but efficiently front-loaded.

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 one-parameter deletion tool, the description covers purpose, usage context, behavioral traits, parameter source, error handling, and return format. It is fully complete given the absence of annotations.

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?

Only one parameter (page_id) with no schema description (0% coverage). The description adds meaning by stating how to obtain the page_id (from list_landing_pages) and what happens if invalid (404 error). This compensates well for the schema gap.

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?

Description clearly states it permanently deletes a landing page, with the verb 'delete' and the resource 'landing page'. It distinguishes itself from the sibling unpublish_landing_page by noting this is permanent.

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?

Explicitly says when to use this tool (permanent deletion) and when to use the alternative unpublish_landing_page (temporary offline). Also mentions error handling for invalid page_id.

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