smartsuite_add_layout_tab

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

The description discloses side effects such as enabling tabs if not already on, first tab mirroring layout, and dry-run preview. This adds context beyond the readOnlyHint=false annotation, without contradiction.

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 a single, dense paragraph that efficiently conveys all necessary information. It is front-loaded with the core action, though the detail could be slightly more structured.

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 lack of output schema, the description thoroughly explains what the tool does, including dry-run behavior and tab enabling logic. It covers all 7 parameters and their interplay comprehensively.

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%, but the description adds meaning by explaining that 'position' is 0-based, 'style' is for tab-bar, 'align' is container-level, and 'confirm' is required to apply. It also notes that description is optional.

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 'Add a tab to an application's record-view layout' with a specific verb and resource, and it distinguishes this tool from siblings like smartsuite_remove_layout_tab and smartsuite_update_layout_tab.

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?

It explicitly mentions requirements: 'Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE' and explains the dry-run behavior. However, it does not explicitly state when not to use it or provide alternatives.

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