smartsuite_create_records

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

The description adds significant behavioral context beyond the readOnlyHint=false annotation: it specifies authentication mode requirements, the dry-run/confirm two-phase execution model, respect for SMARTSUITE_MAX_BATCH_WRITES, and return values (IDs and per-row failures). No contradiction with 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?

Four sentences, front-loaded with purpose, each sentence adding value. No filler. Efficient and clear.

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?

Despite no output schema, the description covers return values, prerequisites, batch limits, and workflow. For a batch create tool with 4 parameters, this is comprehensive.

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 adds the dry-run/confirm workflow context but doesn't significantly elaborate on individual parameter formats beyond what the schema provides. The mention of 'field values keyed by slug' is already in the schema.

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 'Batch-create multiple records in one call.' This is a specific verb+resource, and the name 'smartsuite_create_records' distinguishes it from the singular 'smartsuite_create_record' and other siblings like 'smartsuite_update_records'.

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 explicit prerequisites: requires readwrite/admin mode, dry-run workflow, batch-size cap respect, and a prerequisite to call smartsuite_describe_application. It lacks explicit when-not-to-use guidance, but the name and context suffice.

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