list_supported_save_formats

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

Without annotations, the description carries the full burden of disclosing behavior. It fully describes what the tool returns (Format Name, Extension, Description) and explains its role in the conversion workflow. This is transparent for a read-only query tool.

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 well-structured with sections, bullet points, and a clear returns list. It is slightly verbose with emojis and repetitive phrasing, but every sentence provides useful information and the organization aids readability.

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 description is fully complete for a tool with no parameters and no output schema. It explains the return values, when to use the tool, and how it relates to conversion tools (convert_file, convert_with_options). It gives enough context for an agent to select and invoke it 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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter details, and it does not add any irrelevant information. The schema coverage is 100% as there are no parameters to describe.

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 tool's purpose: to query the list of file formats supported by Aspose.Cells for conversion. It uses a specific verb ('get') and resource ('supported file save/export formats'), and differentiates from sibling tool 'list_supported_load_formats' by focusing on save/export formats.

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 provides usage context: call this tool when a user requests a conversion and you need to verify the correct file extension or availability. It also gives a concrete recommendation to call it before using convert_file or convert_with_options if unsure about the target_format parameter, which is actionable and clear.

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