list_lp_versions

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

With no annotations, the description carries the burden of disclosures. It explains the meaning of previewUrl, including the distinction between the live version's URL and the ?version= form, plus the top-level previewUrl for the current draft. This is valuable context, though it doesn't cover every potential behavior like ordering or pagination.

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 three sentences, front-loaded with the primary purpose, and every sentence adds useful context. No unnecessary words or repetition of schema details.

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?

Despite no output schema, the description explains the key return value (previewUrl) and its subtle behavior, and points to view_lp_version for further details. It covers the essential aspects for an agent to use the tool correctly, though it could mention array structure or ordering.

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?

The schema already documents both parameters fully with 100% coverage. The description adds nothing beyond restating the default for detail, which is already in the schema. Thus the description provides no substantive parameter information beyond structured data.

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 opens with 'List all saved versions of a landing page', clearly stating the verb and resource. It also distinguishes itself from sibling tools by explicitly mentioning view_lp_version for section content, making the purpose 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?

It provides explicit guidance to use view_lp_version when section content is needed, which serves as an alternative and a when-not-to-use signal. The default detail='short' and the mention of detail levels also help the agent decide when to use this vs. zooming into a specific version.

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