publish_landing_page

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

Discloses idempotency, authentication requirements, concurrent request limit, respect for read-only/dry-run modes, and specific HTTP error codes (400, 404). Since no annotations are provided, the description fully covers behavioral traits.

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?

Compact description with every sentence adding value. Starts with the core action, then covers unique behaviors, error handling, and parameter explanation. No fluff.

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?

Fully describes input, output, side effects (idempotent), error states, and authentication limits. Given it has one simple parameter and an output schema referenced, nothing is missing.

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?

Explains the page_id parameter as 'Landing page ID to publish' and tells how to obtain it from list_landing_pages. The input schema only provides title 'Page Id' and type, so the description adds essential context. However, the parameter is a simple ID with no further formatting needs, so 4 is 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?

Clearly states the tool publishes a landing page making it live at its public URL. Distinguishes from sibling tools like unpublish_landing_page and get_landing_page by name-dropping them.

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 mentions when to use alternatives (unpublish_landing_page to take offline, get_landing_page to confirm). Also notes error conditions for when not to expect success (missing content, invalid ID). No explicit when-not to use this tool, but guidelines are clear.

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