smartsuite_restore_field

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

The description discloses behavioral traits beyond annotations: mutation (consistent with readOnlyHint=false), required mode and env variable, dry-run preview, and need for explicit confirmation. No contradictions 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?

The description is concise (two sentences) and front-loaded with the main action and essential requirements. Every sentence adds value without redundancy.

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 tool's complexity (3 parameters, no output schema), the description covers all critical aspects: purpose, prerequisites, input sources, and default behavior. It is complete for agent selection and invocation.

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?

Even though schema coverage is 100%, the description adds meaning by explaining the slug's origin (from smartsuite_list_deleted_fields) and the confirm parameter's default behavior. This enriches the schema's definitions.

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 action ('Restore a soft-deleted field back into its application'), specifying the verb 'Restore' and the resource ('soft-deleted field'). It distinguishes itself from sibling tools like 'smartsuite_list_deleted_fields' and 'smartsuite_delete_field' by focusing on restoration.

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 explicitly states requirements ('readwrite/admin mode AND SMARTSUITE_ENABLE_SCHEMA_WRITE=true'), provides context on inputs ('Supply the applicationId the field belonged to and its slug (from smartsuite_list_deleted_fields)'), and explains behavior ('Dry-run preview unless confirm:true'). This gives clear guidance on when and how to use the tool.

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