new_page_skeleton

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

Annotations already declare readOnlyHint=true, so no side effects. The description adds value by detailing the return shape's structure and how width parameters affect settings.width_section, giving behavioral context beyond the annotation. Consistent with openWorldHint=false.

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?

Single paragraph, front-loaded with purpose and return shape. Slightly verbose in repeating the shape, but each sentence adds value (width guidance, coordinates context). Could be trimmed slightly, but overall well-structured for an agent.

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 3 optional params, no output schema, and annotations providing safety, the description covers the return structure, width behavior, and usage context. It is complete enough for the agent to select and invoke correctly, with no obvious gaps.

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 all 3 parameters with descriptions. The description adds meaning beyond schema by explaining usage rationale (e.g., choosing 1200 for wide/editorial pages, 960 for narrow) and how parameters set canvas width upfront. This enhances the agent's understanding beyond enum values.

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 clearly states it returns an empty page skeleton, specifies the shape (page:[], popup:[], settings, options, cartConfigs), and distinguishes from siblings like create_page by being a read-only template initializer. The verb 'returns' and resource 'top-level page source' are specific and 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?

Provides explicit guidance on when to use desktopWidth 1200 vs 960 (wide/multi-column vs narrow/simple, cloning reference), implying use as a starting template. Does not explicitly state when not to use or give alternatives, but context from sibling tools and the description's conditional advice is sufficient.

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