smartsuite_restore_records

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

Annotations only provide readOnlyHint=false, indicating mutation. The description goes beyond by detailing the need for specific access modes and configuration flags, and it discloses the preview behavior when confirm is not true. No contradictions with annotations. It adds significant behavioral context that annotations alone do not cover.

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 two sentences long, each packed with essential information. The first sentence states purpose and prerequisites, the second explains behavior and data sources. Every word earns its place; no fluff or repetition.

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 has 3 simple parameters, no output schema, and minimal annotations, the description covers prerequisites, behavior, and parameter semantic. It doesn't describe the preview response format, but for a tool with a clear dual behavior, this is a minor gap. Overall, it provides sufficient context for an agent to use the tool correctly.

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 parameters, but the description adds crucial semantics: it explains that confirm controls preview vs actual restore, and it tells users where to find record IDs (delete response, audit log, list_deleted_records). This goes well beyond the schema's minimal 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?

The description starts with a clear verb+resource: 'Restore soft-deleted records from the trash.' It distinguishes this tool from siblings like smartsuite_delete_records and smartsuite_list_deleted_records by specifying it's for restoration from trash, and it mentions prerequisites that separate it from other record operations.

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 when to use the tool (restore soft-deleted records) and provides critical context: it requires readwrite/admin mode and the SMARTSUITE_ENABLE_RESTORE=true flag. It also explains the dual behavior of the confirm parameter (preview vs actual restore) and where to obtain record IDs, giving comprehensive usage guidance.

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