List Supported Save Formats

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

With no annotations present, the description carries the disclosure burden. It explains that the tool returns a list of formats with name, extension, and description, and implies a read-only query by framing it as a lookup. It could be more explicit that no conversion or file modification is performed, but the usage guidance makes the metadata-only behavior clear enough.

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 a clear purpose line, return field breakdown, and numbered usage guidelines. Each section adds distinct value, and the most important 'when to use' information is front-loaded near the top.

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?

There is no output schema, so the description compensates by documenting the exact return fields: format name, extension, and description. Combined with explicit usage guidance and zero parameters, the description gives an agent everything needed 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 tool has zero parameters, so the schema is trivially complete. The baseline of 4 applies because there are no parameter semantics for the description to add, and it appropriately does not invent any.

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 identifies the tool as a query for all file save/export formats supported by Aspose.Cells for conversion, using the specific verb 'query'. It distinguishes this from conversion tools by framing it as a supporting lookup for target_format strings, and the save/export framing differentiates it from the sibling list_supported_load_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 states when to call the tool: when a user requests a conversion and the agent needs to verify extension/availability, and before calling convert_file or convert_with_options when unsure of target_format. It also tells the agent what to do when a requested format is unsupported: recommend the closest alternative.

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