update_landing_page

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

Description adds behavioral context beyond annotations: partial update behavior ('Only provided fields are changed'), error condition (404 for invalid page_id), and lists return fields. Annotations already indicate non-read-only and non-idempotent. Missing concurrency or rate limit info, but overall good transparency.

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?

Very concise: first sentence summarizes, then constraints, alternatives, error, Args list, Returns. Front-loaded and no unnecessary words. Every sentence adds value.

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 7-param tool with 1 required, 0% schema coverage, and output schema present, the description covers all parameters, output, errors, and immutability constraints. It is fully adequate for an agent to use this tool correctly.

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?

With 0% schema coverage, description provides brief but clear parameter descriptions (e.g., 'New internal name' for name, 'Landing page ID. Obtain from list_landing_pages' for page_id). Could explicitly state that null means skip, but the phrase 'Only provided fields are changed' implies this.

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 'Update settings of an existing landing page' with specific verb and resource. It explicitly distinguishes from siblings like create_landing_page, delete_landing_page, publish/unpublish_landing_page, and get_landing_page by noting immutable fields and alternatives for live status changes.

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 when-to-use (updating settings), when-not-to-use (changing list_id/template, changing live status), and alternatives (publish/unpublish, create new page). Also advises inspecting current settings with get_landing_page before updating.

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