save_spreadsheet_asConvert a spreadsheet from cloud storage to a different format and save it as a new file.
Convert a spreadsheet in Aspose Cloud Storage to a different format (e.g., XLSX to PDF) and save it as a new file.
| Name | Required | Description | Default |
|---|---|---|---|
| file_uuid | Yes | ||
| target_format | Yes |
Changes observed during successful MCP inspections.
v26.4.1Input schema / properties / file_tokenRemoved value: -{
- "type": "string"
-}Input schema / properties / file_uuidAdded value: +{
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "file_token",
- "target_format"
-]New value: +[
+ "file_uuid",
+ "target_format"
+]v26.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does indicate that a new file is saved, but it does not disclose storage location, naming, return value, permissions, or whether the original file is preserved. An agent cannot predict side effects beyond the basic conversion.
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 with a useful example. It is front-loaded with the main action and does not waste words, though it could have added more critical detail without becoming verbose.
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 tool has no annotations, no output schema, and no parameter descriptions, and it sits among many similar conversion tools. The description gives only the core operation and leaves the agent without enough information to reliably select or invoke it among the 35 sibling tools.
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 0%, so the description must compensate by explaining file_uuid and target_format. It gives an example format (XLSX to PDF) that hints at target_format's role, but it never explains what file_uuid refers to, acceptable target_format values, or how formats are specified.
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 a specific verb ('Convert'), a resource ('a spreadsheet in Aspose Cloud Storage'), and an outcome ('save it as a new file'). However, many sibling tools also perform conversions, so this description does not explicitly differentiate it from tools like convert_spreadsheet or convert_excel.
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?
There is no guidance about when to use this tool versus the many sibling conversion tools. No alternatives, exclusions, or conditions are mentioned, leaving the agent to guess which conversion/save tool fits the task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.