crm_update_layout

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It merely states 'Update layout configuration' without indicating whether this is a destructive operation, if it requires specific permissions, or what happens to existing layout data. This is insufficient for a mutation tool.

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 short sentence, 'Update layout configuration', which is extremely concise and front-loads the action verb. There is no wasted verbiage.

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?

This tool has two required parameters including a nested object (layout_data) and no output schema or annotations, so the description must compensate. It does not explain the structure of layout_data, what constitutes a valid update, or provide any operational context, leaving a significant gap.

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?

The input schema provides descriptions for both parameters (layout_id and layout_data), giving 100% coverage. The description adds no extra meaning beyond what the schema already states, so it meets the baseline but doesn't exceed it.

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 uses the imperative verb 'Update' with the resource 'layout configuration', clearly indicating the tool's function. While there are sibling tools like crm_update_profile and crm_update_role, the mention of 'layout' distinguishes it from those, though it doesn't elaborate on what 'layout configuration' encompasses.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as fetching existing layouts first with crm_get_layouts, or scenarios where updating a profile or role would be more appropriate.

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