smartsuite_create_form

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

Annotations indicate readOnlyHint=false, so the agent knows this is a write operation. The description adds context: it checks label uniqueness, validates field slugs against the application schema, and supports a dry-run mode. These details go beyond the annotations.

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. It covers all critical information without unnecessary fluff. While not broken into sections for readability, it is concise and front-loaded with the core action and prerequisites.

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?

With 9 parameters and no output schema, the description omits what the tool returns (e.g., the created form object or ID). It covers creation behavior and prerequisites well but lacks completeness on return value, which could hinder agent understanding.

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%, yet the description adds value by explaining the uniqueness constraint on label, the validation of field slugs, and the semantics of the confirm parameter (dry-run vs. create). This supplements the schema's parameter 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 'Create a new form for a SmartSuite application.' The verb and resource are explicit, and the function is distinct from sibling tools like smartsuite_list_forms or smartsuite_update_form.

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 explicit prerequisites: 'Requires readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true.' Also explains the dry-run behavior vs. actual creation via the confirm parameter. However, it does not explicitly mention when not to use or list alternative tools for similar tasks.

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