Create Experience Cloud Page

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

Annotations already mark this as a mutating, non-idempotent operation. The description adds useful behavioral context—URL paths are relative to the site prefix and pages can be standard or custom—but does not disclose potential conflicts, error behavior, or prerequisites beyond needing an existing site.

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 action, then the key distinctions and usage timeline. No redundant restatement of the schema.

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 5-parameter create tool with no output schema, the description supplies enough to select and invoke: what it creates, the supported types, URL semantics, and correct usage ordering. It doesn't explain return values or duplicate handling, but those are not critical for correct invocation.

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 covers 100% of parameters with basic descriptions, so baseline is 3. Description adds meaningful semantics by explaining that 'standard' page types include home, login, profile, object detail, and object list, and by clarifying that url is relative to the site's URL prefix.

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 opens with specific action verb 'Creates a page within an existing Experience Cloud site,' identifying both resource (page) and scope (existing site). It further differentiates from sibling tools by listing page types (standard vs custom), clarifying it is not for site creation.

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?

Provides explicit sequencing: 'Use after creating the site to add additional pages for different content sections,' which tells the agent when to invoke relative to site creation. It does not name an alternative tool or specify when not to use it, so it falls short of a 5.

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