smartsuite_create_view

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

Beyond the readOnlyHint=false annotation, the description discloses behavioral traits: required mode/env var, label uniqueness validation with alternative suggestion, dry-run preview unless confirm:true, field slug validation against schema. No annotation 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 reasonably concise given the tool's complexity. It fronts the purpose and prerequisites, then proceeds logically through parameters and behavior. Each sentence adds value, though it could be slightly more compact.

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 10-parameter creation tool with no output schema, the description covers purpose, prerequisites, parameters, behaviors (dry-run, uniqueness), and distinctions from related tools. It lacks explicit mention of the return value on success, but overall it's highly informative.

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 description coverage is 100%, but the description adds significant meaning: explains label uniqueness logic, enumerates view modes explicitly, describes optional config fields (visibleFields, filters, sort, groupBy), and the filterOperator enum. This goes beyond the 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?

The description starts with 'Create a view (report) in an application,' providing a specific verb and resource. It explicitly distinguishes from forms and dashboards by mentioning alternatives, making the purpose clear and unambiguous.

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?

Prerequisites are explicitly stated ('requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true'). The description explains the uniqueness check for labels and the dry-run confirmation flow. It also directs users to smartsuite_create_form for forms and notes that dashboards are separate.

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