smartsuite_move_attachments

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

The description discloses that files are copied without re-upload (reference existing storage), that the source is cleared by default, that mode can append or replace, and that there is a dry-run mode unless confirm:true. It also mentions a cap on records. This provides full insight into the tool's behavior, matching the readOnlyHint=false annotation.

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 that efficiently communicates all key points. It front-loads the purpose and then details options. While it could be more structured (e.g., bullet points), it is concise and contains no wasted words.

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?

The description covers most behavioral aspects but does not explicitly state the return value or output format. Since there is no output schema, the agent is left to infer the response (likely success/result or preview data). Given the complexity (8 params, mutation tool), this omission is a 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?

Schema coverage is 100% with descriptions for all 8 parameters. The description adds context beyond the schema, such as 'handles reference existing storage — no re-upload' and the dry-run behavior, but the schema already explains individual parameters well. The description adds overall behavioral context but not per-parameter detail.

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 the verb 'move' and the resources 'attachments' and 'file fields'. It explains the core action: copying files from one field to another and optionally clearing the source. This distinguishes it from sibling tools like smartsuite_upload_file or smartsuite_create_record.

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 specifies required access mode ('readwrite/admin'), explains when to use recordId vs allRecords, and describes the mode (append/replace) and clearSource options. It also mentions the dry-run behavior. It lacks an explicit 'when not to use' statement, but the instructions are clear and the tool is unique among siblings.

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