Create Lightning App Builder Page (FlexiPage)

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, indicating a non-destructive write operation. The description adds valuable context that the created page is not automatically activated or assigned, but must be done later via Setup > Lightning App Builder. This goes beyond the annotations by clarifying the post-creation workflow.

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 long, front-loaded with the purpose, and each sentence provides distinct useful information (purpose, supported types + requirements, post-activation note). 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?

Given the moderate complexity and full schema with all parameters described, the description covers the essential aspects: creation, page types, template, conditional object API name, and activation path. It does not explain error behavior or response format, but no output schema exists and annotations cover safety attributes, so the description is sufficiently complete.

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 the baseline is 3. The description repeats the template examples and the conditional requirement for objectApiName that are already present in the schema descriptions. It does not add substantive parameter semantics beyond what the schema already provides.

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 Lightning App Builder page (FlexiPage) via the Metadata API, which is a specific verb+resource. It also lists supported page types (AppPage, RecordPage, HomePage), distinguishing it from sibling tools like sf_create_lightning_app or sf_create_experience_page.

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 usage context: it explains the supported page types, requires the object API name for RecordPage, and notes that pages are activated later via Setup. However, it does not explicitly contrast with alternative tools or state when not to use this tool, so it lacks the 'excluded alternatives' component.

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