create_landing_page_draft

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the page is created in DRAFT state, imposes slug formatting rules, explains the domain default behavior, and requires the featured image to be hosted in HubSpot. These are concrete behaviors beyond the bare 'create' action, though it does not cover error cases or auth requirements.

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 one-sentence summary is front-loaded, followed by a compact per-parameter list with no filler, repetition, or unnecessary prose. Every line adds meaningful information.

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 the 9-parameter surface with no schema descriptions, the description does a thorough job covering each parameter and key behavioral constraints. The output schema exists, so the return value need not be described. The only minor gap is the lack of explicit differentiation from the closely related create_site_page_draft sibling.

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 0%, so the description is the only documentation for all 9 parameters. It explains semantics for every parameter, including the template source ('from list_templates'), slug constraints, ISO language code default, the optional domain behavior, and the nature of layout_sections. This fully compensates for the empty 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 opens with a specific verb and resource: 'Create a new landing page in DRAFT state.' It clearly distinguishes this from sibling tools like create_site_page_draft by naming the resource and state, and the summary is not a tautology.

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 useful contextual guidance, such as using list_templates to fill template_path and only supplying domain when the portal has several domains. However, it never explicitly says when to choose this tool over alternatives like create_site_page_draft or mentions when not to use it, so the routing is left to inference.

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