slide_list_file_restores

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

With no annotations, the description carries the burden of behavioral disclosure, but it is a simple read/list operation and 'List' clearly implies that. It adds useful context about what a file restore is, but it does not describe pagination behavior, default ordering, or what the response contains.

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 efficient sentence that front-loads the primary action and resource, then adds a clarifying parenthetical. There is no redundancy or filler.

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?

For a straightforward paginated list with six optional parameters and no output schema, the description is minimally adequate. It names the resource and its creation-date filter, but it omits any mention of return format, default pagination, or how this tool fits into a workflow with file-restore siblings.

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 description coverage is 100%, so the schema already documents all six parameters with reasonable detail. The description's phrase 'filterable by creation date' adds conceptual meaning for created_after/created_before, but it does not explain limit, offset, or sorting behavior beyond what the schema provides.

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 states a specific verb and resource: 'List file restores', and clarifies the concept with 'a snapshot exposed for browsing/downloading individual files'. It is not a tautology and identifies the object of the operation, though it does not explicitly distinguish itself from sibling tools like slide_list_file_restore_pushes.

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 no guidance on when to choose this tool over alternatives such as slide_get_file_restore, slide_browse_file_restore, or slide_list_file_restore_pushes. It implies usage through 'List file restores' but does not state exclusions or conditions that should route an agent to a different sibling.

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