list_supported_load_formats

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

With no annotations, the description carries the full burden. It clearly discloses the read-only nature of the tool and describes the return structure (Format Name, Extension, Description). It also adds useful context about the difference between load and save formats, implying potential read-only/write-only limitations. Minor gap: it doesn't mention whether the list is exhaustive or version-dependent, but overall strong.

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 clear sections and front-loaded title. It is slightly verbose for a zero-param tool, but every section adds value (purpose, returns, usage). The bullet lists improve scannability. Minor redundancy in repeating 'load formats (Input)' vs 'save formats (Output)' but acceptable.

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 simple query tool with no params and no output schema, the description is complete. It explains what the tool returns (three fields), when to use it, and how it relates to sibling tools. There is no missing context needed for an agent to invoke and interpret results 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 adds no parameter-specific information because none exist, which is appropriate. It does explain the output fields, but parameter semantics are not applicable.

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: 'Use this tool to query the list of all source file formats that Aspose.Cells can read (load).' It specifies the verb 'query', the resource 'supported load formats', and explicitly distinguishes from sibling list_supported_save_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 provides explicit when-to-use guidance: 'Call this tool when a user wants to upload or process a non-standard Excel file...' and lists concrete scenarios (before upload_file, when user asks about CSV). It also warns to distinguish load vs save formats, which are alternatives.

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