Export an application

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

With no annotations provided, the description carries the disclosure burden. It reveals the noteworthy behavioral trait that output is truncated when returned inline, and warns that exports are large. However, it doesn't disclose what the JSON structure contains, whether the export is a full app snapshot, or any failure/edge-case behavior.

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?

Two sentences, both earning their place. Front-loaded with the primary action, then the key use-case distinction (outputPath recommended vs inline truncation). Zero filler; every word adds information.

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 tool with only 2 simple flat params, 100% schema coverage, and no output schema, this description is reasonably complete. It covers the main decision point (file vs inline), the truncation caveat, and the size concern. It could briefly note what the exported JSON contains, but this is a minor gap for a simple export tool.

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 coverage is 100%, so both parameters (outputPath, applicationId) are documented in the schema. The description adds semantic weight by recommending outputPath and explaining why (exports are large, inline returns are truncated), which goes beyond what the schema states.

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 verb (Exports), resource (an application), and output format (as JSON). It distinguishes this from sibling tools like appsmith_list_applications or appsmith_clone_application by emphasizing the export-to-file behavior. The purpose is specific and unambiguous.

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 clear guidance on when to use the outputPath (recommended because exports are large), giving practical usage context. It's clear on when to use each mode, though it doesn't explicitly name alternative sibling tools or exclusion conditions.

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