smartsuite_set_display_logic

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

Annotations indicate readOnlyHint: false, confirming it's a write operation. The description adds important details: required permissions, the ability to remove logic via clear:true, and the dry-run behavior (preview unless confirm:true). It also explains the conditions structure and common comparisons. No contradictions.

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 well-structured and front-loaded with the core purpose. It includes an example and lists common comparisons. Slightly long but all sentences earn their place. Minor reduction due to length but no fluff.

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 complexity (7 parameters, nested conditions, three target types), the description covers behavior, permissions, and usage patterns. It does not mention return values, but that is acceptable since no output schema exists. Overall, it is complete enough for an agent to use 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?

Schema coverage is 100%, so baseline is 3. The description goes well beyond the schema by explaining target types (field slug, section__ slug, tab id), conditions array format with example, common comparisons, and the clear/confirm flags. This adds significant value for an agent.

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 states the verb 'Add, modify, or remove' and the resource 'display (visibility) logic on a field, section, or tab', with the specific purpose 'show it only when conditions on other fields are met'. This clearly distinguishes it from sibling tools like smartsuite_set_field_visibility, which likely handles static visibility instead of conditional logic.

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 clear context: it's used for conditional visibility, requires readwrite/admin + SMARTSUITE_ENABLE_SCHEMA_WRITE, and mentions dry-run preview unless confirm:true. It gives an example and lists common comparisons. However, it does not explicitly contrast with smartsuite_set_field_visibility or state when not to use it.

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