unpublish_landing_page

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

No annotations provided, but description covers authentication, rate limits, modes (read-only/dry-run), error behavior (404), and return format. Fully transparent.

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?

Concise, front-loaded with main action, followed by essential details in logical order. Every sentence adds value.

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 simple tool, description covers action, parameter, usage guidance, alternatives, errors, and return. Complete for effective use.

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?

Single parameter page_id has no schema description (0% coverage); description adds meaning by stating it's the ID to unpublish and where to obtain it.

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 the action ('take a published landing page offline') and distinguishes from siblings by mentioning publish_landing_page and delete_landing_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?

Explicitly provides when-to-use (reversible unpublish), when-not (permanent removal via delete), and how to get the page_id from list_landing_pages.

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