create_landing_page

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

Annotations only indicate readOnlyHint=false, etc., which is minimal. The description adds valuable behavioral context: it returns the public URL and explicitly mentions that subscribers flow into your contact list, a side effect beyond simple creation. This goes beyond what annotations convey.

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?

Two sentences, front-loaded with the primary purpose and followed by key output and side-effect information. Every word adds value; no filler or redundancy.

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 create tool with no output schema, the description covers the primary return value (public URL) and the key side effect (subscribers to contact list). It is complete enough for an agent to anticipate the behavior, though it does not detail error cases or prerequisites, which are not critical for a simple create operation.

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 description coverage is 100%, so parameters are fully documented in the schema. The description adds general context about email capture and contact list, which relates to tags and cta_text, but it does not specifically enhance understanding of any parameter beyond the schema descriptions.

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 creates a hosted landing page with an email capture form, which is a specific verb+resource combo. It distinguishes this from sibling tools like create_form and create_campaign by specifying 'hosted landing page' and the email capture function. Returns the public URL adds clarity about the output.

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 clear context for when to use: when you want a hosted landing page that captures emails and sends subscribers to your contact list. It does not explicitly name alternatives or exclusions, but the use case is well implied.

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