slide_list_file_restore_pushes

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

With no annotations, the description carries the behavioral disclosure burden. It adds useful semantic context by explaining that pushes are the act of copying a restored file back to a protected system, which helps the agent understand the operation's role. The verb 'List' implies a read-only behavior, but the description does not explicitly mention read-only status, output shape, pagination behavior, or any side effects.

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, focused sentence that front-loads the core action and adds a concise clarifying parenthetical. Every word contributes meaning, and there is no repetition of schema details.

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 9-parameter list endpoint with complete schema descriptions, the description is adequate: it identifies the resource, the parent file restore context, and the filtering dimension. Given the absence of an output schema and annotations, some additional detail about return content could help, but the description plus schema is sufficient for an agent to invoke 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?

The input schema covers 100% of the 9 parameters with descriptions, so the schema already documents the parameter semantics well. The description adds only a general mention of start/end time filtering, but no additional meaning beyond the schema. Baseline 3 is appropriate.

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 action ('List') and a specific resource ('push operations') with a helpful parenthetical defining what a push is in this context: copying a restored file back to a protected system. This clearly distinguishes it from list_file_restores and even from get_file_restore_push by establishing that it is the plural listing operation, though it does not explicitly name those siblings.

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 implies when to use the tool: when listing push operations for a file restore, with optional start/end time filtering. However, it gives no explicit guidance about when to prefer this over slide_get_file_restore_push or other related list endpoints, nor does it state any exclusions or prerequisites.

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