smartsuite_update_layout_section

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

Discloses schema-write permission and dry-run mechanism beyond annotations (which only indicate non-read-only). Also notes clearing description with empty string. Adds useful behavioral context.

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?

Three concise sentences with no superfluous content. Front-loads purpose and key constraints. Excellent economy of words.

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?

Covers essential behavioral aspects (preview, permission, clearing description) despite no output schema. Could be slightly more detailed on return value but adequate given complexity.

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 coverage is 100% (baseline 3). Description adds semantic value by explaining dry-run via confirm param and clearing description with empty string, which are not fully captured in schema descriptions.

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?

Clearly states verb (update), resource (layout section), and specific attributes (title, description, collapsed, hidden). Distinguishes from sibling tools like add_layout_section.

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 context on permission requirement ('Requires schema-write') and preview behavior ('Dry-run preview unless confirm:true'). No explicit when-not or alternatives, but enough guidance for typical use.

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