Create Page Layout

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

Annotations already convey readOnly=false, destructive=false, and idempotent=true. The description adds context about page layout purpose and configuration (sections, related lists), but does not detail side effects like overwriting existing layouts, permission requirements, or assignment behavior beyond creation. It does not contradict annotations.

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, front-loaded with the core action, and every sentence adds value: defining what it creates, explaining the domain concept, and indicating how to structure the layout configuration.

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 full schema coverage and annotations, the description is sufficiently complete. It explains the purpose, key configuration elements, and relationship to profiles/record types. It lacks explicit output/return details, but no output schema exists and the operation is clearly a creation action.

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 mentions 'sections with fields' and 'related lists', which aligns with schema parameters, but adds no extra semantic detail beyond what schema property descriptions already provide.

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 'Creates a Page Layout for a Salesforce object' with a specific verb and resource, and distinguishes it from sibling tools like create_compact_layout or assign_layout_to_record_type by explaining what page layouts do (control fields, related lists, buttons).

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 implies when to use this tool: when you need to define record detail/edit page composition for an object. It also notes that layouts are assigned to profiles and record types, hinting at context, but does not explicitly name alternatives or provide exclusions.

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